agentleFS
wundercorpwundercorp/loki/skills/AGENTS.md

loki / skills

AGENTS.md28 starsChanged 2 months agoMITView on GitHub

Applies on top of the root AGENTS.md. Long-form: website/docs/developer-guide/creating-skills.md; user docs: website/docs/user-guide/features/skills.md, curator.md. - skills/ — built-in, loadable by default, organised by category (skills/github/, skills/mlops/). - optional-skills/ — heavier/niche skills shipped but NOT active; installed via loki skills install official/<category>/<skill> (adapter tools/skills_hub_official.py OptionalSkillSource). Categories: autonomous-ai-agents, blockchain, communication, creative, devops, email, health, mcp, migration, mlops, productivity, research, security, web-development. Reviewing a skill PR: check the target directory — heavy-dep or niche skills go to optional-skills/. name, description, version, author, license, platforms…

  • Reads credentials

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Distinctive:

    Every new or modernised skill — bundled, optional, or contributed — meets all of these before merge:

    line 26
  2. Very specific:

    scripts/, references/, templates/: Don't make the model inline-write parsers or non-trivial logic every call — ship a helper script …

    line 50

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

skills/ + optional-skills/ — bundled skills, authoring standards, curator

Applies on top of the root AGENTS.md. Long-form: website/docs/developer-guide/creating-skills.md; user docs: website/docs/user-guide/features/skills.md, curator.md.

Two surfaces

  • skills/ — built-in, loadable by default, organised by category (skills/github/, skills/mlops/).
  • optional-skills/ — heavier/niche skills shipped but NOT active; installed via loki skills install official/<category>/<skill> (adapter tools/skills_hub_official.py OptionalSkillSource). Categories: autonomous-ai-agents, blockchain, communication, creative, devops, email, health, mcp, migration, mlops, productivity, research, security, web-development.

Reviewing a skill PR: check the target directory — heavy-dep or niche skills go to optional-skills/.

SKILL.md frontmatter

name, description, version, author, license, platforms (OS gate: [macos], [linux, macos], ...), metadata.loki.tags, metadata.loki.category, metadata.loki.related_skills, metadata.loki.config (config.yaml settings the skill needs — stored under skills.config.<key>, prompted during setup, injected at load). Top-level tags: / category: are accepted and mirrored from metadata.loki.* by the loader.

Authoring standards (HARDLINE — enforced by tests/skills/test_authoring_standards.py)

Every new or modernised skill — bundled, optional, or contributed — meets all of these before merge:

  1. description ≤ 60 chars, one sentence, ends with a period. Long descriptions bloat listings and dilute attention when many skills load. State the capability, not the implementation; no marketing words ("powerful", "comprehensive", "seamless", "advanced"); don't repeat the name. Check: len(re.search(r'^description: (.*)$', text, re.M).group(1)) <= 60.
  2. Prose references native Loki tools or the MCP servers the skill expects, in backticks (terminal, web_extract, read_file, patch, search_files, vision_analyze, browser_navigate, delegate_task). Never name shell utilities the agent has wrapped: grep → search_files, cat/head/tail → read_file, sed/awk → patch, find/ls → search_files target='files'. MCP dependencies are named with setup in ## Prerequisites. Third-party CLIs and pipelines are fine inside script files, not as the headline surface.
  3. platforms: gating is audited against actual script imports. POSIX-only primitives (fcntl, termios, os.setsid, os.kill(pid, 0), /proc, hardcoded /tmp, signal.SIGKILL, bash heredocs, osascript, apt, systemctl) require a platform declaration. Fix cross-platform first (tempfile.gettempdir, pathlib.Path, psutil.pid_exists, Python filtering instead of grep); gate narrower only when the dependency is genuinely platform-bound.
  4. author credits the human first. External contributor's real name + GitHub handle first, "Loki Agent" second. A commit authored as "Loki Agent" (they drafted with Loki) is replaced with the human's name — credit the human, not the tool.
  5. Modern section order: # <Skill> Skill, 2–3 sentence intro (what it does and doesn't), ## When to Use, ## Prerequisites, ## How to Run, ## Quick Reference, ## Procedure, ## Pitfalls, ## Verification. ~200 lines for a complex skill, ~100 simple. Cut intro fluff, marketing prose, and env-var re-explanations already in Prerequisites.
  6. scripts/, references/, templates/. Don't make the model inline-write parsers or non-trivial logic every call — ship a helper script and reference it by skill-relative path.
  7. Tests at tests/skills/test_<skill>_skill.py, stdlib + pytest + unittest.mock only, no live network. Run scripts/run_tests.sh tests/skills/test_<skill>_skill.py -q.
  8. .env.example additions sit in a clearly delimited block. Contributor copies of the file are usually stale; edits outside the skill's own block are dropped during salvage.

No offset/limit pagination on skill-loading tools — the agent must read a skill fully (root). The salvage/modernisation checklist for external skill PRs is references/new-skill-pr-salvage.md in the loki-agent-dev skill.

Curator (skill lifecycle)

Background maintenance that tracks usage on agent-created skills and auto-archives stale ones; archives go to ~/.loki/skills/.archive/ and are restorable. Core agent/curator.py (review loop, auto-transitions, LLM review prompt) + agent/curator_backup.py (pre-run tar.gz snapshots); CLI loki_cli/curator.py → loki curator status|run|pause|resume|pin|unpin|archive|restore| prune|backup|rollback; telemetry tools/skill_usage.py owns ~/.loki/skills/.usage.json (use_count, view_count, patch_count, last_activity_at, state active/stale/archived, pinned). Config curator: — enabled, interval_hours, min_idle_hours, stale_after_days, archive_after_days, backup.*; its LLM calls route through auxiliary (agent/AGENTS.md).

Invariants: touches only created_by: "agent" skills (bundled + hub-installed are off-limits); never deletes — archive is the maximum; pinned skills are exempt from every auto-transition and the LLM review; skill_manage(action="delete") refuses pinned skills while patch/edit/write_file/ remove_file still work so the agent can keep improving them.

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.