Link to skill

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.