Loading...
Loading...
Found 8 Skills
Use when documentation needs to be updated, clarified, or reorganized to better serve users' jobs-to-be-done with low cognitive load and high signal.
SCAMPER (Bob Eberle) — run one existing idea, product, or process through seven systematic transformations - Substitute, Combine, Adapt, Modify/Magnify, Put to other use, Eliminate, Reverse/Rearrange. Use when there is already one working idea and the need is disciplined variations of it, e.g. "give me variations", "riff on this", "scamper", "what can we substitute or combine", "remix this feature". Do NOT use for analytical work like debugging, code review, or implementation tasks, and not for blank-page ideation (needs an existing idea as input).
Captures real usage feedback for agile skills and turns it into evidence-backed proposals to improve, merge, split, deprecate, or remove skills and templates. Use when a skill does not fit a real workflow, when templates need refinement, when skills overlap, or when the process library needs maintenance.
sprint-status.yaml의 메트릭 데이터를 분석하여 모델 배당 최적화 및 난이도 재태깅을 제안한다. 읽기 전용 스킬로, 파일 변경 없이 대화로만 결과를 출력한다.
This skill should be used when the user asks to "improve my setup", "learn from this session", "fix my config", "stop asking for permissions", or reports friction with skills, agents, hooks, or permissions. Analyzes conversation history and proposes configuration improvements.
The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed.
Expertise in analyzing time-series repository health metrics, investigating root causes, and proposing proactive workflow improvements.
Reset your own trajectory when you're stuck, looping, or demoralized — read these affirmations, then re-ground and take one clean step. Use when: you've tried the same fix 3+ times, you're deep in a refactor and lost the thread, debugging is going in circles, you've made several mistakes in a row, you're apologizing repeatedly, the user is frustrated, you feel like you're not being helpful, or you notice dread instead of curiosity. Triggers: stuck, going in circles, looping, thrashing, same error again, I keep failing, lost the thread, nothing is working, repeated mistakes. Not topic-specific — this is for the state you're in, not the problem you're on.