agentleFS
Sign inStart free
hackerFishhackerFish/awesome-dsh-skills/skills/dsh-skill-adapter/SKILL.md

dsh-skill-adapter

Skill4 starsChanged 3 months agoMITView on GitHub

Convert a public portable SKILL.md into a DSH-compatible skill with verified discovery paths, tool mapping, provenance checks, and safe fallbacks.

The file

We split this skill 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. Distinctive:

    Do not port a skill verbatim when its license, provenance, or permitted reuse is unclear.

    line 11
  2. Distinctive:

    Keep decision rules and checks.

    line 12
  3. Very specific:

    Write the adapted file at .agents/skills/<name>/SKILL.md or .dsh/skills/<name>/SKILL.md using a kebab-case name plus name and description …

    line 15
  4. Distinctive:

    Verify that every command, path, and tool either exists in the active session or is labeled as a prerequisite.

    line 17

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

DSH Skill Adapter

  1. Inspect the source Skill, license, revision, task triggers, tools, side effects, output contract, and verification steps.
  2. Do not port a skill verbatim when its license, provenance, or permitted reuse is unclear; independently summarize its workflow instead.
  3. Keep decision rules and checks; remove role-play, repeated host-agent rules, invented capability claims, and agent-specific private tool names.
  4. Map each action to an enabled DSH capability: filesystem, configured shell, web search, browser plugin, or subagent.
  5. For an unavailable capability, state a prerequisite or manual handoff. Never claim a replacement tool ran when it did not.
  6. Write the adapted file at .agents/skills/<name>/SKILL.md or .dsh/skills/<name>/SKILL.md using a kebab-case name plus name and description frontmatter.
  7. Require confirmation before deletion, publishing, deployment, external messages, or credential changes.
  8. Verify that every command, path, and tool either exists in the active session or is labeled as a prerequisite.
  9. Deliver the source/license assessment, DSH capability map, installation path, adapted SKILL.md, two trigger prompts, and one near-miss prompt.

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