agentleFS
Sign inStart free
freemtyfreemty/labmate/.agents/skills/project-skill/SKILL.md

project-skill

Skill25 starsChanged 2 months agoMITView on GitHub

Use when LabMate architecture, compatibility boundaries, release contracts, or known pitfalls are needed.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Run tests/test-hooks.sh, test-platform-compat.sh, test-context-contract.sh and test-scripts.sh for a release.

    line 18

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

LabMate — Project Knowledge

  • 12 portable skills; five Claude named agents with ordinary-subagent/main-thread fallback. Read-paper packets retain source coverage and page/equation/figure locators.
  • Four lifecycle handlers: existing session context, silent commit-maintenance records, once-per-session pending summary before compaction, Git advisory. Ordinary directories do not require initialization. Hooks do not grant permission.
  • Pipeline state and experiment structures are owned by typed scripts. Pending maintenance uses atomic local state; failed commands are not completed commits.
  • Package, both manifests and README badges share version 0.11.0. Release checks do not change user installations; commit inner repository before the outer marketplace gitlink. Plugin install and legacy links are alternatives.
  • Run tests/test-hooks.sh, test-platform-compat.sh, test-context-contract.sh and test-scripts.sh for a release. Payload fixtures do not prove live host trust.

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.

Check your setup, free