agentleFS
peter-tu-zynkrpeter-tu-zynkr/zynkr-skill-builder/skills/2-sales-consultant/consult-status-report/SKILL.md

consult-status-report

Skill21 starsChanged 50 days agoNo licenceView on GitHub

Generate the weekly CLIENT-FACING status email for ONE consulting engagement. Reads the CRM deal's tasks / activities / notes plus the newest [Notes] / [Plan] / [BRD] / [UAT] docs in the client's numbered [N] Drive folder, derives health / progress / blockers / next milestone, renders the 專案狀態看板-style HTML dashboard, and creates a Gmail DRAFT addressed to the deal's client contact — NEVER auto-sends. Trigger on /consult-status-report or when Peter says "客戶週報", "顧問案週報", "寫給客戶的進度報告", "客戶進度信", "draft the client status update", "status email for <client>", "engagement weekly for the client" — any weekly/status ask that NAMES a client or engagement. Distinct from consult-session-notes (files ONE session into a [Notes] Doc; this skill READS those docs as evidence), from consult-adoption-reporter (post-go-live usage TELEMETRY report as a Doc, not a weekly email), and from consult-governance (may flag that the client weekly is DUE — the drafting happens here). BOUNDARY: bare "週報" / "weekly report" / "project weekly update" WITHOUT client context stays with project-status-update (the internal tracker-Sheet weekly), which also owns ALL scheduled / cron / recurring weekly runs — this skill is Peter-invoked per engagement and must not hijack those triggers.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.