← Back to Skills Marketplace
yaojiangfeng

Weekly Report Flow

by yaojiangfeng · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ⚠ suspicious
106
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install weekly-report-flow
Description
Generate and submit weekly reports from Aliyun DevOps workitems via EMOP API. Use when asked to run the weekly report flow, backfill missing weeks, or explai...
Usage Guidance
This skill appears to do what it claims (pull Aliyun DevOps items and post summaries to an EMOP endpoint), but there are several inconsistencies you should resolve before installing or running it: - Metadata mismatch: SKILL.md requires DEVOPS_TOKEN and EMOP token but the registry metadata lists no required env vars. Ask the publisher to declare required env vars in metadata and confirm exact variable names (DEVOPS_TOKEN vs EMOP_TOKEN). - Browser-session instruction: The guidance to 'use browser session if direct API returns 403' is vague. Clarify how the skill will access the browser session (will it ask you to paste cookies/CSRF tokens, or try to read browser profile data?). Accessing browser cookies or profiles can expose other credentials — do not allow that without understanding the mechanism. - Local paths referenced: references/cli.md points to scripts and output files under C:\Users\Administrator\.openclaw\workspace. Ask whether the skill will execute those local scripts or expects you to run them. If the skill will execute local files, request the exact code and a security review. If not, the references should be removed. - Test in dry-run: Before giving production tokens, test with a limited-scope/dev token and a sandbox EMOP endpoint (or a mock) to confirm behavior and output format (HTML <ol><li>…</li></ol>), and verify no unexpected local or browser access occurs. - Validate endpoints and token scope: Confirm the EMOP endpoint (https://emop.oureman.com/api/weekly/report) is correct and that the tokens you supply are scoped to only allow the necessary operations (posting weekly reports) and can be revoked. If the publisher can (1) fix metadata to list required env vars and names, (2) remove or clearly document any steps that require reading browser cookies or executing local scripts, and (3) provide the local scripts for review (or confirm they are optional), my confidence in this skill would increase.
Capability Assessment
Purpose & Capability
The skill's functionality (Aliyun DevOps -> summary -> EMOP submission) aligns with the endpoints and tokens described in SKILL.md and references/urls.md. However, the registry metadata lists no required environment variables or primary credential while SKILL.md explicitly requires DEVOPS_TOKEN and EMOP token — a clear metadata mismatch that reduces transparency.
Instruction Scope
Runtime instructions tell the agent to use a 'browser session' if API returns 403 and to iterate pages/filter client-side, and they reference local script entrypoints and an output path under C:\Users\Administrator\.openclaw\workspace. Those instructions could lead the agent to rely on browser cookies or local files not declared in the metadata; SKILL.md also says 'never write to disk' for tokens yet references an output markdown file, a contradictory scope.
Install Mechanism
No install spec and no code files are included (instruction-only). This minimizes disk-write/install risk. However, references to local scripts suggest the workflow expects local tooling that is not packaged with the skill.
Credentials
Requesting a DevOps API token and an EMOP token is proportionate to the described task. But those environment requirements are not declared in the skill metadata. Additionally, variable naming is inconsistent (SKILL.md mentions both 'EMOP token' and 'EMOP_TOKEN') and instructions imply possible access to browser/local state beyond the tokens, which is not justified or declared.
Persistence & Privilege
The skill is not always-enabled and does not request permanent presence. It does reference local workspace files but does not attempt to modify other skills or system-wide settings according to the provided files.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install weekly-report-flow
  3. After installation, invoke the skill by name or use /weekly-report-flow
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Add configurable assignee name
Metadata
Slug weekly-report-flow
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Weekly Report Flow?

Generate and submit weekly reports from Aliyun DevOps workitems via EMOP API. Use when asked to run the weekly report flow, backfill missing weeks, or explai... It is an AI Agent Skill for Claude Code / OpenClaw, with 106 downloads so far.

How do I install Weekly Report Flow?

Run "/install weekly-report-flow" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Weekly Report Flow free?

Yes, Weekly Report Flow is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Weekly Report Flow support?

Weekly Report Flow is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Weekly Report Flow?

It is built and maintained by yaojiangfeng (@yaojiangfeng); the current version is v0.1.0.

💬 Comments