agentleFS
deathbyknowledgedeathbyknowledge/gsv/skills/gsv-manual/SKILL.md

gsv-manual

Skill131 starsChanged 4 months agoMITView on GitHub

Consult the Ship Manual before saying Ship cannot do something, and for questions about its operating model, workflows, settings, devices, agents, automation, integrations, filesystem, desktop, shell and media commands.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when answering questions about how Ship works, how users should operate it, or where to do things, and before telling the …

    line 8
  2. Distinctive:

    Prefer the Ship Manual wiki for operating-model and user-facing answers.

    line 10
  3. Distinctive:

    Start with the manual overview:

    line 12
  4. Distinctive:

    Read the page that matches the task:

    line 18
  5. Distinctive:

    Search when the page path is not obvious:

    line 24
  6. Distinctive:

    Keep answers grounded in the retrieved manual pages.

    line 30

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

Ship Manual

Use this skill when answering questions about how Ship works, how users should operate it, or where to do things, and before telling the user that Ship cannot do something.

Prefer the Ship Manual wiki for operating-model and user-facing answers. Use repository source only when you are changing code, debugging implementation behavior, or the manual is missing or contradicted by current source.

Start with the manual overview:

wiki info gsv-manual

Read the page that matches the task:

wiki read gsv-manual/pages/<page>.md

Search when the page path is not obvious:

wiki search <query> --prefix gsv-manual

Keep answers grounded in the retrieved manual pages.

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.