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

consult-governance

Skill21 starsChanged 51 days agoNo licenceView on GitHub

The weekly hygiene sweep across the WHOLE consulting portfolio — inventory every numbered [N] engagement folder under the consult Drive parent AND every open consult deal in the CRM, diff the two against six invariants (deal↔folder backlink, kickoff-doc presence, session-note recency, [N] numbering continuity, activity pulse, artifact chain), and emit a zh-TW ready-to-apply changelist in the chat. Strictly READ-ONLY — it proposes fixes named to the owning skill but never applies one: no Doc creation, no folder moves, no CRM writes, not even a deal-note append. Trigger on /consult-governance or when Peter says "顧問案健檢", "檢查顧問專案", "顧問 portfolio 盤點", "案子有沒有漏", "consult drift check", "audit the engagement folders", or "portfolio hygiene sweep". Distinct from admin-governance (local _INDEX.md ↔ Drive KNOWLEDGE governance — a different universe), from consult-status-report (ONE engagement, client-facing, writes a Gmail draft; this is ALL engagements, internal, writes nothing), and from consult-intake / consult-project-specialist (they OWN the fixes this report proposes — folder creation, numbering, backlinks).

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are 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.

  • 2

    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 372,429 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.