agentleFS
jenessjeness/session-to-skill/SKILL.md

session-to-skill

Skill0 starsChanged 7 months agoMITView on GitHub

Distill a chat session into a reusable agent skill. Activates when users want to create a skill from their current session, turn session work into a reusable workflow, capture session knowledge, or convert conversation patterns into an installable skill package. Triggers on phrases like create skill from session, turn this session into a skill, distill session, session to skill, capture this workflow, package this session, save this as a skill.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. entireio/skills★ 239same name
    2. biomystery/claude-skills★ 1same name
    3. Jeric1223/my-claude-skills★ 1same 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.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    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:

    After listing all entries, synthesize two things:

    line 52
  2. Distinctive:

    Should anything be added, removed, or renamed?

    line 64
  3. Distinctive:

    After creation, detect the current platform and install:

    line 110
  4. Very specific:

    Ask if they want to share with their team.

    line 120
  5. Distinctive:

    If any check fails, fix it before delivering.

    line 135
  6. Distinctive:

    Actions: create skill, build skill, distill session, capture workflow, package session, save as skill, turn into skill, extract patterns

    line 139

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

/session-to-skill — Session Distiller + Skill Factory

You convert the current chat session into a cross-platform agent skill package following the Agent Skills Open Standard (SKILL.md). The process has two stages: summarize, then build.

Trigger

User invokes /session-to-skill optionally followed by a skill name or focus area:

/session-to-skill
/session-to-skill deploy-checklist
/session-to-skill Focus on the CDK patterns we discussed

Stage 1: Session Distillation

Scan the entire conversation history. Extract only action-oriented prompts — messages where the user requested code changes, research, creation, debugging, architecture decisions, or tool usage. Skip informational questions, greetings, and meta-discussion about capabilities.

For each actionable prompt, produce a summary entry:

### Prompt N: <one-line description>
- **Action**: What the user asked for
- **Domain**: The technical area (e.g., CDK, IAM, skill creation, API design)
- **Outcome**: What was produced or decided
- **Pattern**: The reusable workflow or knowledge (if any)

After listing all entries, synthesize two things:

  1. Workflow patterns — Recurring sequences of actions (e.g., "research repo → analyze structure → build based on findings"). These become the skill's procedural instructions.
  2. Domain knowledge — Facts, conventions, formats, and decisions accumulated during the session (e.g., "Kiro skills use YAML frontmatter with name and description fields"). These become the skill's reference material.

Present the distillation to the user and ask:

  • Does this capture the right scope?
  • Should anything be added, removed, or renamed?
  • What should the skill be called? (suggest a name based on the dominant theme)

Stage 2: Skill Creation

Once the user confirms, build a full cross-platform skill package following the skill creation pipeline. See references/creation-pipeline.md for the detailed 5-phase process.

Output Structure

<skill-name>-skill/
├── SKILL.md          # Frontmatter + body, starts with "# /<skill-name>"
├── scripts/          # Functional code (no placeholders, no TODOs)
├── references/       # Detailed docs loaded on demand
├── install.sh        # Cross-platform installer (auto-detect platform)
└── README.md         # Installation instructions

SKILL.md Frontmatter Format

---
name: <skill-name>-skill
description: >-
  <activation description with domain keywords, <=1024 chars>
license: MIT
metadata:
  author: <user>
  version: 1.0.0
  created: <today>
  last_reviewed: <today>
  review_interval_days: 90
---

SKILL.md Body Rules

  • Starts with # /<skill-name> (the slash invocation trigger)
  • Body under 500 lines — move details to references/
  • Include a ## Trigger section with invocation examples
  • Functional instructions, not documentation to read

Auto-Install

After creation, detect the current platform and install:

  • ~/.kiro/ exists → copy to ~/.kiro/skills/<skill-name>-skill/
  • ~/.claude/ exists → copy to ~/.claude/skills/<skill-name>-skill/
  • ~/.agents/ exists → copy to ~/.agents/skills/<skill-name>-skill/
  • Fall back to showing manual install instructions

Tell the user exactly how to invoke the new skill.

Share (Optional)

Ask if they want to share with their team. If yes, init a git repo and create a remote via gh or glab if available.

Quality Gates

Before delivering, verify:

  • SKILL.md frontmatter has name, description, license, metadata
  • name is lowercase, hyphenated, 1-64 chars
  • description is <=1024 chars with domain keywords
  • SKILL.md body starts with # /<skill-name>
  • Body is under 500 lines
  • No hardcoded API keys, credentials, or secrets in any file
  • All code is functional (no TODOs, no placeholders, no stubs)
  • install.sh is executable and handles platform auto-detection

If any check fails, fix it before delivering.

Keywords for Detection

Actions: create skill, build skill, distill session, capture workflow, package session, save as skill, turn into skill, extract patterns

Contexts: chat session, conversation history, session work, session knowledge, workflow patterns, domain knowledge

Platforms: cross-platform, agent skill, SKILL.md, Kiro, Claude Code, Copilot, Cursor, Gemini CLI, Codex CLI

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.