skill-simplify

Other Community

Repo stars 2,029
Author repo Claude-Code-Workflow

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functionality los…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Input Processing”, “TodoWrite Pattern”, “Core Rules”, “Error Handling”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-simplify directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Input Processing / TodoWrite Pattern / Core Rules” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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').length

TodoWrite 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) from descriptive (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

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Other
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @catlog22 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-simplify.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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](phases/01-analysis.md) | Extract functional inventory, identify redundancy, validate pseudo-code format |
| 2 | [phases/02-optimize.md](phases/02-optimize.md) | Apply simplification rules, fix format issues |
| 3 | [phases/03-check.md](phases/03-check.md) | Verify functional integrity, validate format |

## Input Processing

```javascript
const targetPath = input.trim()
const targetFile = targetPath.endsWith('.md') ? targetPath : `${targetPath}/SKILL.md`
const originalContent = Read(targetFile)
const originalLineCount = originalContent.split('\n').length
```

## TodoWrite Pattern

```javascript
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

1. **Preserve ALL functional elements**: Code blocks with logic, agent calls, data structures, routing, error handling, input/output specs
2. **Only reduce descriptive content**: Flowcharts, verbose comments, duplicate sections, examples that repeat logic
3. **Never summarize algorithm logic**: If-else branches, function bodies, schemas must remain verbatim
4. **Classify code blocks**: Distinguish `functional` (logic, routing, schemas) from `descriptive` (ASCII art, examples, display templates) — only descriptive blocks may be deleted

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Input Processing → TodoWrite Pattern → Core Rules → Error Handling
terms    -> Phase Reference Documents · Preserve ALL functional elements · Only reduce descriptive content · Never summarize algorithm logic · Classify code blocks · Merge equivalent variants · Fix format issues · Validate pseudo-code
files/cmd -> ${targetPath}/SKILL.md · Phase 1: Analyzing ${targetFile} · functional · descriptive
body sha256 -> be4705fbf1ec