agentleFS
matthewwong525matthewwong525/WongStack/.agents/skills/services/SKILL.md

services

Skill7 starsChanged 11 days agoMITView on GitHub

Use an outside tool or service (Notion, Stripe, a CRM…): call it through the company app, or write code that calls it.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run services to find the key and its notes page.

    line 11
  2. Very specific:

    Run api <key>, then api <key> <call> before you call or write code.

    line 12
  3. Very specific:

    Add what you learn about one call to its description, not to the notes page.

    line 14

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Services

The company app holds each service's key, so you call it through node scripts/company-api.mjs. The services list owns the why and the rest.

  1. Run services to find the key and its notes page. Read the notes page for the key, its levels and its limits.
  2. Run api <key>, then api <key> <call> before you call or write code. Never open schema/services/<key>/openapi.json itself: the short view is the part you need.
  3. For a call that api doesn't list, read the service's guide, then call it with <key>.read or <key>.change. When the helper says the call isn't added yet, run the record command it prints, then write the call's summary (what we use it for) and description (how we use it, its quirks) in openapi.json.
  4. Add what you learn about one call to its description, not to the notes page.
  5. In code, type the answer with app/worker/services/<key>.ts, and test it on the saved examples: service examples.

Download now (ZIP)

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.