agentleFS
glasser-aiglasser-ai/skills/AGENTS.md

skills

AGENTS.md6 starsChanged 2 months agoMITView on GitHub

Guidance for agents working in this repository. Humans: read CONTRIBUTING.md instead; it is the same rules with the reasoning. Markdown skills for agents that run paid research on Glasser. It is also a Claude Code plugin marketplace (.claude-plugin/) and is installable with npx skills add glasser-ai/skills. There is no build step and no runtime code outside .github/scripts/. The Glasser mechanism (auth, search, inspect, run, balance rules) is documented at https://glasser.ai/SKILL.md and shipped by glasser-ai/plugins. Nothing here duplicates it. Node 20…

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Every SKILL.md carries the block in templates/glasser-prereq.md verbatim, between the H1 and the first ##.

    line 30
  2. Distinctive:

    No HTML comments, no CJK characters, under 500 lines.

    line 32
  3. Distinctive:

    No provider names in skill names or process steps.

    line 33
  4. Distinctive:

    No execution channels: a skill ends at a result, it does not send, post, publish, or buy.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

AGENTS.md

Guidance for agents working in this repository. Humans: read CONTRIBUTING.md instead; it is the same rules with the reasoning.

What this repository is

Markdown skills for agents that run paid research on Glasser. It is also a Claude Code plugin marketplace (.claude-plugin/) and is installable with npx skills add glasser-ai/skills. There is no build step and no runtime code outside .github/scripts/.

The Glasser mechanism (auth, search, inspect, run, balance rules) is documented at https://glasser.ai/SKILL.md and shipped by glasser-ai/plugins. Nothing here duplicates it.

Layout

.claude-plugin/
  plugin.json          plugin manifest; "skills": "./skills"
  marketplace.json     marketplace manifest; one plugin, source "./"
.github/
  scripts/validate.mjs check every skill and the repo-level invariants
  scripts/sync.mjs     regenerate the README table, marketplace count and per-skill prerequisite block
  workflows/           validate on PR and push to main; sync check on main
skills/<name>/SKILL.md one skill per directory
templates/             SKILL.template.md and glasser-prereq.md; outside skills/ on purpose

Invariants

  • name in frontmatter equals the directory name.
  • Frontmatter has exactly name, description, metadata.version, metadata.category.
  • description is on one line with description:, 1 to 1024 characters.
  • Every SKILL.md carries the block in templates/glasser-prereq.md verbatim, between the H1 and the first ##.
  • No ](../ or ](/ links; skills are copied out alone.
  • No HTML comments, no CJK characters, under 500 lines.
  • No provider names in skill names or process steps. Describe the capability to search for and what to confirm on inspect.
  • No execution channels: a skill ends at a result, it does not send, post, publish, or buy.
  • No .mcp.json here, no tools/ directory, no shared/ directory.
  • skills/glasser/ is the one mirror of glasser.ai/SKILL.md: body byte-identical to the source, frontmatter name, description, version, metadata.source, metadata.category, no prerequisite block. Regenerate it with node scripts/sync-glasser-skill.mjs; never edit it by hand.
  • Nothing under templates/ is named SKILL.md; installers would treat it as a skill.
  • README table, marketplace skill count and every skill's prerequisite block are generated; sync.mjs --check enforces all three.

Commands

node .github/scripts/validate.mjs   # all checks; exit 1 on any error
node .github/scripts/sync.mjs       # rewrite README table, marketplace count, prerequisite blocks
node .github/scripts/sync.mjs --check

Node 20 or later, no dependencies.

Adding a skill

  1. cp templates/SKILL.template.md skills/<name>/SKILL.md and write it.
  2. node .github/scripts/sync.mjs
  3. node .github/scripts/validate.mjs
  4. Branch skills/<name>, conventional commit feat(<name>): add skill, PR with the new-skill template.

Changing a skill

Bump metadata.version in the same PR. Patch for fixes, minor for new dimensions or triggers. To change the prerequisite wording, edit templates/glasser-prereq.md and run sync.mjs; commit the source and the rewritten skills together.

Versioning

plugin.json version and marketplace.json metadata.version share one number and move together: minor for a new skill, patch for changes to existing ones, major for repo-wide restructuring. Per-skill versions live in each SKILL.md and move independently.

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.