Menü
Use when you've identified a recurring pattern worth abstracting into a skill
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when processing conversations to extract reusable knowledge (entities, facts, processes)
Use after completing any task to extract reusable patterns
Use before starting any task to find relevant skills
Use when an existing skill needs updating based on new evidence
Advanced Python development guidance with focus on architecture, design patterns, code quality, type safety, and modern best practices. Use when designing Python systems, refactoring codebases, implementing complex features, reviewing architecture decisions, applying design patterns, or ensuring code follows best practices for maintainability, testability, and performance.
| name | skill-creation |
| description | Use when you've identified a recurring pattern worth abstracting into a skill |
| trigger_pattern | When 2+ similar processes exist or a recurring pattern is identified |
| tags | ["meta","creation","induction"] |
| version | 1 |
| is_protected | true |
| q_value | 0.5 |
| q_update_count | 0 |
NO SKILL WITHOUT 2+ SIMILAR PROCESSES.
A skill must be abstracted from concrete evidence, never from a single instance or pure speculation.
Decision Tree:
├── Found 2+ similar Processes in Neo4j?
│ └── YES → Candidate for skill creation
├── Same pattern applied successfully 2+ times?
│ └── YES → Candidate for skill creation
├── Only 1 instance of the pattern?
│ └── NO → Wait for more evidence
├── Pattern is project-specific?
│ └── NO → Only if generalizable beyond the project
└── Pattern is a one-time debugging step?
└── NO → Debugging steps are NOT skills
Use ProcessSearchTool to find similar processes:
processes = search_processes("trigger pattern description")
Require:
From the concrete processes, extract:
Before creating, verify:
Use SkillCreateTool with:
debug-memory-leak, NOT debugMemoryLeakdebug-, extract-, optimize-, handle-debug-memory-leak, NOT debug-issue# Skill Name
## When to Use
[Clear trigger condition]
## Steps
1. [First step]
2. [Second step]
3. [...]
## Examples
[Concrete example of applying this skill]
## Anti-patterns
[What NOT to do]
## Boundary Conditions
[When this skill does NOT apply]