agentleFS
Sign inStart free
KamicyusKamicyus/skill-forge/skills/link-to-skill/SKILL.md

link-to-skill

Skill0 starsChanged 4 months agoMITView on GitHub

Turns a URL (tweet, X article, blog post, doc) into a reusable agent skill draft in one step. Use when the user shares a link and says "make this a skill", "learn this", "turn this into a skill", or shares a tips/technique link asking to internalize it. Inspired by Hermes Agent's /learn feature.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. kartikkabadi/skills★ 9same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user shares a link and says "make this a skill", follow this flow.

    line 8
  2. Distinctive:

    If the source is behind a paywall/login and can't be fetched: ask the user for a screenshot and distill from the image.

    line 33

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

Link-to-Skill — Generate a Skill from a URL

When the user shares a link and says "make this a skill", follow this flow. Goal: turn an external technique/pattern into a permanent, triggerable skill in a single step.

Flow

  1. Fetch the content (by source):
    • X tweet/article/thread → use your available X/Twitter tool; fetch the full thread if it's a thread
    • Web page → use your available scraping/fetch tool (markdown output preferred)
  2. Distill: extract the TRANSFERABLE technique. Stories, engagement bait, and revenue claims are discarded; only repeatable steps, rules, and checklists remain. The core question: "When this skill triggers 6 months from now, which behavior should change?"
  3. Collision check: list existing skills (ls ~/.claude/skills/) and read their descriptions.
    • A skill already doing the same job → DON'T create a new one; add a section to the existing skill (dedup rule).
    • Partial overlap → state the difference to the user in 1 sentence, let them decide.
  4. Write the draft: ~/.claude/skills/<kebab-name>/SKILL.md
    • Frontmatter: name + description (include concrete English trigger phrases)
    • End the description with the source: Source: <URL> (YYYY-MM-DD)
    • Body: short, imperative, step-by-step — no storytelling, only behavior
  5. Report: give the bare file path + say in 1 sentence when the skill will trigger. The user deletes it if they don't like it.

Rules

  • Skill body ≤60 lines. If it's growing, the distillation failed — go back and distill again.
  • Unverifiable claims in the source ("I made $62K/month") are NEVER carried into the skill; take only the technique.
  • If the source is behind a paywall/login and can't be fetched: ask the user for a screenshot and distill from the image.
  • The generated skill loads automatically in the next session; do NOT try to invoke it via the Skill tool in the same session (it isn't registered yet).

Credit

Inspired by Hermes Agent's /learn feature.

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