Skills That Outlive the Session

/skillify and /adapt-skill for Amplifier

A workflow you perfect in one session dies when it ends — and foreign skills don't speak Amplifier

Two new user-invocable slash commands in the Amplifier skills bundle fix both halves of that problem.

And they're not a proposal — they've already shipped.

Both already shipped into microsoft/amplifier-bundle-skills, backed by 27 passing tests

/skillify and /adapt-skill are user-invocable slash commands on the tracked branch of microsoft/amplifier-bundle-skills — merged, invocable, and tested.

Shipped & merged · bundle v1.1.0

This is real. So why did it matter enough to build?

27
tests passing (14 skillify + 13 adapt-skill)
27
skill directories in the bundle
The Tension

The genuinely useful process you just worked out lives only in this conversation

Close the tab and it's gone. Live session knowledge is fragile and unrepeatable — you'd have to reconstruct it from scratch next time.

/skillify is the fix: it captures that live session before it vanishes.

/skillify reads the session, interviews you, then writes a complete SKILL.md

It analyzes the conversation and interviews you to confirm structure — turning a one-off into a reusable skill saved to disk.

That covers capturing what you built. But what about skills you already own?

  1. 1Consult skills-assist
  2. 2Analyze the session
  3. 3Interview the user
  4. 4Write the SKILL.md
  5. 5Test the skill
  6. 6Review and save

/adapt-skill translates a Claude Code or Cursor skill into Amplifier-native form

It maps foreign tool names, paths, and frontmatter — turning a skill built for another assistant into one that speaks Amplifier's conventions.

Both mechanisms share one thing that keeps the output honest.

Both defer to skills-assist and bake in a real test step before saving

Step 1 of each loads skills-assist as the source of truth for Amplifier skill conventions. A dedicated test step verifies the skill before it's saved — trustworthy, not just generated.

That test discipline shows up in how fast they could ship.

One morning: /skillify polished, then /adapt-skill landed 4m36s later — with its own tests

On 2026-04-08, Brian Krabach polished skillify at 09:06, then committed adapt-skill at 09:10 — shipped together with a 178-line test suite. The tooling had matured enough to ship a new tested skill almost as fast as it could be conceived.

Two siblings from one continuous work session.

4m36sbetween the skillify polish and adapt-skill landing
178lines of test suite shipped with adapt-skill
The Takeaway

Skills should be captured and ported — not rebuilt from scratch

/skillify captures the live session; /adapt-skill translates the foreign one. Together they make hard-won process durable and portable, as tested, reusable Amplifier-native SKILL.md files.

Perfect the workflow once. Keep it forever.

Sources

Research Methodology

Data as of: 2026-04-08 (latest verified commit); research re-derived from a local checkout of microsoft/amplifier-bundle-skills.

Feature status: Shipped and merged into microsoft/amplifier-bundle-skills; both skills user-invocable and covered by 27 passing tests. Bundle version 1.1.0.

Repository: origin ramparte/amplifier-bundle-skills, upstream microsoft/amplifier-bundle-skills (NOT michaeljabbour/amplifier-skill, whose git tree contains no skillify/adapt-skill paths).

Commands run:

Gaps: No merged PR number could be tied to skillify (2bdec3b) or adapt-skill (3656c46) — gh pr list --search <sha> --state all returned empty. The framing "adapt-skill was born from running /skillify" could NOT be verified from any commit, PR, or doc and is deliberately omitted.

Primary contributor: Brian Krabach — author of skillify (2bdec3b), the skillify enhancement (016316a), and adapt-skill (3656c46).

More Amplifier Stories