agentleFS
ShawhinTShawhinT/non-coding-skills/engagements/SKILL.md

engagements

Skill40 starsChanged 13 days agoNo licenceView on GitHub

Use this skill whenever Shaw mentions creating, updating, querying, or wrapping a paid client engagement. Triggers include: \"create an engagement for X\", \"X just paid the invoice\", \"log the engagement\", \"what's the engagement ID for Y\", \"wrap up [Client Name]'s intensive\", \"mark X as delivered\", \"X's session moved\", \"fill in Stripe data for E###\", \"update engagement status\", \"look up the engagement for X\", \"did X pay yet\". Also fires for auditing/syncing the ledger: \"audit/sync the engagements\", \"is the engagement data up to date\", \"reconcile E###\", or the daily scheduled sync. Also fires when a CRM workflow signals \"deal closed\" (kickoff for a new row), or when a new ABA Trainings/Calls page needs linking to an existing engagement. This skill governs the Engagements database in ABA (Master) — the project ledger that tracks one row per won, invoiced project. The CRM (Nurture) database tracks the relationship; this database tracks the work.\n

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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 350,495 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.