skill-simplify
- Repo stars 2,029
- Author updated Live
- Author repo Claude-Code-Workflow
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @catlog22 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-simplify
description: SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize con…
category: other
runtime: no special runtime
---
# skill-simplify output preview
## PART A: Task fit
- Use case: SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functionality lost. Triggers on "simplify skill", "optimize skill", "skill-simplify"..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Input Processing / TodoWrite Pattern / Core Rules” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functionality lost. Triggers on "simplify skill", "optimize skill", "skill-simplify".”.
- **02** When the source has headings, the agent prioritizes “Input Processing / TodoWrite Pattern / Core Rules” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Input Processing / TodoWrite Pattern / Core Rules”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-simplify
description: SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize con…
category: other
source: catlog22/Claude-Code-Workflow
---
# skill-simplify
## When to use
- SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functio…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Input Processing / TodoWrite Pattern / Core Rules” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-simplify" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Input Processing / TodoWrite Pattern / Core Rules
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Skill Simplify
Three-phase pipeline: analyze functional inventory, apply optimization rules, verify integrity.
Phase Reference Documents (read on-demand):
| Phase | Document | Purpose |
|---|---|---|
| 1 | phases/01-analysis.md | Extract functional inventory, identify redundancy, validate pseudo-code format |
| 2 | phases/02-optimize.md | Apply simplification rules, fix format issues |
| 3 | phases/03-check.md | Verify functional integrity, validate format |
Input Processing
const targetPath = input.trim()
const targetFile = targetPath.endsWith('.md') ? targetPath : `${targetPath}/SKILL.md`
const originalContent = Read(targetFile)
const originalLineCount = originalContent.split('\n').lengthTodoWrite Pattern
TodoWrite({ todos: [
{ content: `Phase 1: Analyzing ${targetFile}`, status: "in_progress", activeForm: "Extracting functional inventory" },
{ content: "Phase 2: Optimize", status: "pending" },
{ content: "Phase 3: Integrity Check", status: "pending" }
]})Core Rules
- Preserve ALL functional elements: Code blocks with logic, agent calls, data structures, routing, error handling, input/output specs
- Only reduce descriptive content: Flowcharts, verbose comments, duplicate sections, examples that repeat logic
- Never summarize algorithm logic: If-else branches, function bodies, schemas must remain verbatim
- Classify code blocks: Distinguish
functional(logic, routing, schemas) fromdescriptive(ASCII art, examples, display templates) — only descriptive blocks may be deleted - Merge equivalent variants: Single/multi-perspective templates differing only by a parameter → one template with variant comment
- Fix format issues: Nested backtick template literals in code fences → convert to prose; hardcoded option lists → flag for dynamic generation; workflow handoff references → ensure execution steps present
- Validate pseudo-code: Check bracket matching, variable consistency, structural completeness
- Quantitative verification: Phase 3 counts must match Phase 1 counts for functional categories; descriptive block decreases are expected
Error Handling
| Error | Resolution |
|---|---|
| Target file not found | Report error, stop |
| Check FAIL (missing functional elements) | Show delta, revert to original, report which elements lost |
| Check WARN (descriptive decrease or merge) | Show delta with justification |
| Format issues found | Report in check, fix in Phase 2 |
Decide Fit First
Design Intent
How To Use It
Boundaries And Review