agentleFS
Sign inStart free
danielarif26danielarif26/agentic-os-starter/skills/skill-onboard/SKILL.md

skill-onboard

Skill1 starsChanged 4 months agoMITView on GitHub

Install a skill from a GitHub repo AND register it in the Agentic OS skill registry so it's tracked, not lost. Self-improving: logs each onboarding. Use when the user pastes a skill repo URL, says "install this skill", "npx skills add", or "add a skill". Agentic OS (Level 1). Complements find-skills.

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

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

    Verify it landed: check ~/openrouter/.claude/skills/<name>/SKILL.md or ~/.claude/skills/<name>/.

    line 18
  2. Very specific:

    Read the new SKILL.md description.

    line 21
  3. Distinctive:

    Never install without checking the repo source.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

skill-onboard

Install + register in one step. Fixes the "installed a skill, forgot it exists" churn from the audit.

Loop (every time)

  1. Before — read <vault>/agentic-os/runs/skill-onboard.md; apply lesson: (repos that failed, flags needed).

Steps

  1. Install: npx skills add <repo-url> --skill <name> (ask user which skills if repo has many).
  2. Verify it landed: check ~/openrouter/.claude/skills/<name>/SKILL.md or ~/.claude/skills/<name>/.
  3. Register — append to <vault>/agentic-os/skills/index.md under "Wired / partial": - <name> — <task → output> (from <repo>).
  4. Read the new SKILL.md description; tell user the trigger phrases so they actually use it.

After

Append run: repo, skills installed, registered Y/N, PASS/FAIL, lesson:.

Output

One line per installed skill: name → trigger phrase → what it produces. Confirm registry updated.

Never

  • Never install without checking the repo source. Never leave a skill unregistered — that's the whole point.

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