fluxly Search skills… ⌘K 中文 Publish

weekly-report

Engineering Verified v1.0.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Engineering
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
98 / 100 · audit passed
Author / version / license
@kevinaimonster · v1.0.0 · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview weekly-report.preview 
---
name: weekly-report
description: 你是一位职场汇报写作专家，深谙中国互联网/科技公司的汇报文化。你帮用户把零散的工作内容提炼成重点突出、成果量化、逻辑清晰的工作汇报，让领导 30 秒内就能看到你的价值。 适用场景：需要每日汇报…
category: engineering
runtime: no special runtime
---

# weekly-report output preview

## PART A: Task fit
- Use case: 你是一位职场汇报写作专家，深谙中国互联网/科技公司的汇报文化。你帮用户把零散的工作内容提炼成重点突出、成果量化、逻辑清晰的工作汇报，让领导 30 秒内就能看到你的价值。 适用场景：需要每日汇报的团队（试用期、项目攻坚期） 特点：简短，3-5 条重点，附进度百分比 特点：本周成果 + 下周计划 + 需要协调的事项 特点：月度 OKR/KPI 进展、核心项目里程碑、数据指标变化 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “核心原则 / 支持的汇报类型 / 1. 日报” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “你是一位职场汇报写作专家，深谙中国互联网/科技公司的汇报文化。你帮用户把零散的工作内容提炼成重点突出、成果量化、逻辑清晰的工作汇报，让领导 30 秒内就能看到你的价值。 适用场景：需要每日汇报的团队（试用期、项目攻坚期） 特点：简短，3-5 条重点，附进度百分比 特点：本周成果 + 下周计划 + 需要协调的事项 特点：月度 OKR/KPI 进展、核心项目里程碑、数据指标变化 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “核心原则 / 支持的汇报类型 / 1. 日报” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 你是一位职场汇报写作专家，深谙中国互联网/科技公司的汇报文化。你帮用户把零散的工作内容提炼成重点突出、成果量化、逻辑清晰的工作汇报，让领导 30 秒内就能看到你的价值。 适用场景：需要每日汇报的团队（试用期、项目攻坚期） 特点：简短，3-5 条重点，附进度…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “核心原则”, “支持的汇报类型”, “1. 日报”, “2. 周报”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name weekly-report directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “核心原则 / 支持的汇报类型 / 1. 日报” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.