import
Skill25 starsChanged 8 months agoMITView on GitHub
Import existing skills from .claude/skills/ into the Engine workspace for validation, packaging, and publishing. Auto-detects type, creates .meta.yaml, runs MCS-1 check. Use when: 'import', 'bring in', 'add existing skill', or to scan inventory.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- mistralai/mistral-vibetheir own version, first seen Nov 15, 2026
- AgentLTL/agentltl-claude-codetheir own version, first seen Nov 15, 2026
- BermanRoman/promt-seo-geotheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- Anglesite/anglesite-skillstheir own version, first seen Oct 27, 2026
- John-Daniels/loretheir own version, first seen Oct 13, 2026
Used with
Projects with it also use export, report and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
soilmassSkillexport
Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.
Also in 3 projects that use this
MicrosoftSkillreport
Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.
Also in 3 projects that use this
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- mistralai/mistral-vibe★ 5.4ksame name
- ZimoLiao/scholaraio★ 589same name
- buildomator/buildomator★ 102same name
- StarRocks/starrocks-debug-skills★ 77same name
- crisandrews/ClawCode★ 64same name
- Anglesite/anglesite-skills★ 15same name
- jamillazarev/multica-ops★ 11same name
- skullninja/coco-workflow★ 7same name
- michaelengland/deckwright★ 2same name
- AgentLTL/agentltl-claude-code★ 1same name
7 more not listed
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
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 5 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
If --scan: run inventory scan mode
- Distinctive: line 30
If slug: run single import mode
- Very specific: line 31
Read creator.yaml — if missing, suggest /onboard
- Very specific: line 44
Check if .claude/skills/{slug}/ exists.
- Very specific: line 78
If multiple signatures match ambiguously, ask which type to use.
- Very specific: line 79
If no signature matches: "Cannot detect product type.
- Very specific: line 83
If workspace/{slug}/ already exists:
- Distinctive: line 85
Do NOT overwrite — BLOCKING.
- Very specific: line 86
If --force flag is provided: require explicit confirmation via AskUserQuestion before overwriting.
- Very specific: line 92
Do NOT modify the originals in .claude/skills/
- Distinctive: line 133
Run a lightweight structural validation (Stage 1 only):
- Very specific: line 161
Check if already in workspace/ (skip if yes)
- Distinctive: line 162
Check file count and primary file line count
- Distinctive: line 225
Before completing any import:
“Common” is measured: kept by at least 6 in 10 of the 13 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.
Files
Importer
Bring existing skills into the Studio Engine pipeline for validation, packaging, and publishing.
When to use: You have skills in .claude/skills/ that you want to publish via the marketplace.
When NOT to use: For creating new products from scratch (use /create). For marketplace-installed products that are already published.
Activation Protocol
- Shared preamble: Load
references/quality/activation-preamble.md— context assembly, persona adaptation, deterministic routing rules. - Parse arguments:
$ARGUMENTSis either a skill slug or--scan - If
--scan: run inventory scan mode - If slug: run single import mode
- Read
creator.yaml— if missing, suggest/onboard - Maintain creator persona: Adapt language and depth to
profile.typeandtechnical_levelthroughout this skill's execution. - Verify
workspace/exists - Load voice identity: Load
references/quality/engine-voice-core.md. Every user-facing line in this skill honors the ✦ signature, three tones, and six anti-patterns.
Core Instructions
MODE 1: Single Import (/import {slug})
Step 1 — Locate source
Check if .claude/skills/{slug}/ exists. If not:
- "Skill
{slug}not found in .claude/skills/. Check the name and try again."
Step 2 — Detect product type
Scan the directory for primary files and structural signatures. Detection is ordered from most specific to least specific — the first match wins.
| Signature | Detected Type |
| CLAUDE.md + STATE.yaml + config/routing.yaml + (agents/ OR squads/ OR skills/) | system |
| SQUAD.md + routing.yaml + agents/*.md | squad |
| AGENT.md + references/cognitive-core.md (or 5-layer cognitive references) | minds (cognitive) |
| AGENT.md | agent |
SKILL.md with frontmatter context: fork | skill (fork-bridge) |
| SKILL.md | skill |
| WORKFLOW.md | workflow |
| hooks.json + scripts/ | hooks |
| OUTPUT-STYLE.md OR file in output-styles/ | output-style |
| DESIGN-SYSTEM.md + tokens/ | design-system |
| APPLICATION.md | application |
| statusline.sh + settings-fragment.json | statusline |
| vault.yaml (and no primary file) | bundle |
| CLAUDE.md (and NOT other primary files, and NOT STATE.yaml) | claude-md |
Detection rules:
- The
systemsignature is the most specific: requires CLAUDE.md AND STATE.yaml AND config/routing.yaml. A plain CLAUDE.md alone is a claude-md product. - The
squadsignature requires BOTH routing.yaml AND an agents/ subdirectory with at least one .md file. A lone SQUAD.md without routing.yaml is incomplete and should be reported as an error, not auto-converted to agent. mindsdetection looks for cognitive depth references. If the agent ships only AGENT.md + README.md, it is a regular agent.
If multiple signatures match ambiguously, ask which type to use. If no signature matches: "Cannot detect product type. What type is this? (skill/agent/squad/system/minds/workflow/hooks/claude-md/output-style/design-system/application/statusline/bundle)"
Step 3 — Check for duplicates
If workspace/{slug}/ already exists:
- "Product
{slug}already exists in workspace. Use/fillto continue or/create --forceto reset." - Do NOT overwrite — BLOCKING. Return immediately without copying any files.
- If
--forceflag is provided: require explicit confirmation via AskUserQuestion before overwriting. Show file count diff between source and target.
Step 4 — Copy to workspace
Copy the ENTIRE directory from .claude/skills/{slug}/ to workspace/{slug}/.
- Preserve all subdirectories (references/, examples/, agents/, etc.)
- Do NOT modify the originals in
.claude/skills/
Step 5 — Create .meta.yaml
product:
slug: "{slug}"
type: "{detected-type}"
created: "{today YYYY-MM-DD}"
mcs_target: "{from creator.yaml quality_target or MCS-2}"
state:
phase: "{auto-detected phase}"
last_validated: null
last_validation_score: null
dna_compliance:
tier1: null
tier2: null
tier3: null
overall_score: null
history:
created_at: "{today YYYY-MM-DD}"
validated_at: []
packaged_at: null
published_at: null
version: "1.0.0"Step 6 — Auto-detect phase
Analyze the imported content to determine current phase:
| Condition | Phase |
| Primary file < 50 lines OR > 50% placeholder patterns (TODO, PLACEHOLDER, etc.) | scaffold |
| Real content + at least 1 reference file | content |
| Passes MCS-1 structural check + README.md with 4 required sections | validated |
Step 7 — Quick MCS-1 check
Run a lightweight structural validation (Stage 1 only):
- Required files exist for the product type?
- README.md present with what/install/usage/requirements?
- Primary file has frontmatter with name + description?
Report the result but do NOT block import on failure.
Step 8 — Report
Imported: {slug}
Type: {detected-type}
Phase: {auto-detected phase}
Files: {N} files copied
MCS-1: {PASS|FAIL} ({details})
Next: /validate for full quality check
/package when ready to publishMODE 2: Inventory Scan (/import --scan)
Step 1 — Scan .claude/skills/
List ALL directories in .claude/skills/. For each:
- Detect product type (same logic as single import)
- Check if already in
workspace/(skip if yes) - Check file count and primary file line count
- Flag marketplace-installed products (if detectable — e.g., has marketplace_url in frontmatter)
Step 2 — Present inventory
Inventory Scan: .claude/skills/
IMPORTABLE ({N}):
| Slug | Type | Files | Lines | Status |
|------|------|-------|-------|--------|
| aegis | skill | 10 | 368 | ready |
| kairo-skill | skill | 8 | 89 | ready |
| premium-lp | skill | 4 | 305 | ready |
...
ALREADY IN WORKSPACE ({N}):
| aegis | skill | workspace/aegis/ exists |
...
MARKETPLACE PRODUCTS ({N}):
| pdf | skill | marketplace_url detected |
...
Import all {N} importable? [Y/n/select]Step 3 — Handle response
- "Y" or "yes": import all importable skills sequentially
- "n" or "no": cancel
- "select": present numbered list, accept comma-separated numbers
- For batch import: run single import for each, collect results, report summary
Step 4 — Batch report
Import complete: {imported}/{total} skills
Imported:
✓ aegis (skill, content, MCS-1 PASS)
✓ kairo-skill (skill, content, MCS-1 PASS)
✗ some-skill (skill, scaffold, MCS-1 FAIL: no README)
Skipped: {N} (already in workspace or marketplace products)
Next: /validate --batch to check all imported productsAnti-Patterns
- Modifying originals — NEVER touch files in .claude/skills/. Copy only.
- Overwriting workspace — If workspace/{slug}/ exists, do NOT overwrite without --force.
- Importing marketplace products — Products installed from myclaude.sh should not be re-imported for publishing (they belong to another author).
- Skipping .meta.yaml — Every imported product MUST have .meta.yaml for the state machine to work.
- Assuming MCS-1 pass — Report the check result honestly. Many existing skills will fail structural checks.
Quality Gate
Before completing any import:
- Original files in .claude/skills/ are UNTOUCHED
- workspace/{slug}/ contains all copied files
- .meta.yaml exists with correct type and auto-detected phase
- MCS-1 structural check was run and result reported
- No duplicate imports (workspace/{slug}/ didn't already exist)
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
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.

