eureka
Capture technical breakthroughs and transform them into actionable, reusable documentation. Use this skill when the user has achieved a significant technical insight, solved a hard problem, discovered a non-obvious solution, or wants to document a breakthrough moment. Also trigger when the user mentions "eureka", "breakthrough", "document this insight", "capture this discovery", or wants to turn a technical win into reusable knowledge.
- Installs
- 117
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/feiskyer/claude-code-settings --skill eureka- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads eureka automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Eureka
Capture technical breakthroughs and transform them into actionable, reusable knowledge assets while context is fresh.
Process
1. Capture the Breakthrough
When invoked, immediately gather the essential details:
- What was the problem? The specific challenge or blocker faced.
- What was the insight? The key realization that unlocked the solution.
- What changed? Concrete before/after differences (metrics, behavior, code).
- Is there a minimal working example? Request one if not provided.
Ask clarifying questions if any of these are unclear, but act fast — capture while context is fresh.
2. Create the Breakthrough File
Create a structured markdown file at breakthroughs/YYYY-MM-DD-[brief-name].md using today's date and a concise kebab-case name derived from the breakthrough.
Use this template:
# [Descriptive Title]
**Date**: YYYY-MM-DD
**Tags**: [relevant, searchable, tags]
## One-Line Summary
A single sentence capturing the core insight.
## The Problem
What was the challenge? What wasn't working? Include specific error messages, performance numbers, or behavioral descriptions.
## The Insight
The key realization or discovery. What made this non-obvious? Why did previous approaches fail?
## Implementation
Minimal working code demonstrating the solution:
\`\`\`[language]
# concrete code example
\`\`\`
## Impact
| Metric | Before | After |
|--------|--------|-------|
| [relevant metric] | [value] | [value] |
## Reusable Pattern
Abstract the specific solution into a general principle that can be applied elsewhere:
- **When you see**: [symptom or situation]
- **Consider**: [the general approach]
- **Because**: [why it works]
## Related Resources
- Links to relevant documentation, issues, or discussions
3. Update the Index
Update breakthroughs/INDEX.md with a new entry. If the index file does not exist, create it with this structure:
# Breakthrough Index
| Date | Title | Tags | Link |
|------|-------|------|------|
| YYYY-MM-DD | [Title] | [tags] | [link to file] |
Append the new entry to the table, keeping entries in reverse chronological order (newest first).
4. Extract Reusable Patterns
After documenting, help the user identify:
- Is this pattern applicable to other parts of the codebase?
- Could this become a lint rule, test, or automated check?
- Should this be shared with the team?
Key Principles
- Act fast: Capture insights while context is fresh — don't over-polish on first pass.
- Be specific: Include concrete metrics, error messages, and code. Vague breakthroughs are not reusable.
- Think reusable: Always extract the generalizable pattern from the specific solution.
- Stay searchable: Use consistent tags and clear titles so breakthroughs can be found later.
Your Task
Document the breakthrough based on what the user describes:
- If the description is clear, proceed directly to creating the breakthrough file
- If details are missing, ask focused clarifying questions first
- Create the file, update the index, and highlight the reusable pattern
FAQ
What does the eureka skill do?
Capture technical breakthroughs and transform them into actionable, reusable documentation. Use this skill when the user has achieved a significant technical insight, solved a hard problem, discovered a non-obvious solution, or wants to document a breakthrough moment. Also trigger when the user mentions "eureka", "breakthrough", "document this insight", "capture this discovery", or wants to turn a technical win into reusable knowledge.
How do I install eureka?
Run npx skills add https://github.com/feiskyer/claude-code-settings --skill eureka in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/eureka/ (personal) or .claude/skills/eureka/ (project).
Which AI agents can use eureka?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is eureka safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains eureka?
It is published by feiskyer in feiskyer/claude-code-settings. It has 117 recorded installs.
More from feiskyer/claude-code-settings
spec-kit-skill
feiskyer/claude-code-settings
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow. Triggers: "spec-kit", "speckit", "constitution", "specify", ".specify/", "规格驱动开发", "需求规格".
kiro-skill
feiskyer/claude-code-settings
Open the skill to read its SKILL.md instructions.
codex-skill
feiskyer/claude-code-settings
Leverage OpenAI Codex/GPT models for autonomous code implementation, code review, and plan review. Triggers: "codex", "use gpt", "gpt-5", "let openai", "full-auto", "adversarial review", "second opinion review", "用codex", "让gpt实现", "对抗式审查", "让codex审查计划", "第二意见". Use this skill whenever the user wants to delegate coding tasks to OpenAI models, run code or plan reviews via codex, get a second-opinion review from a different model, or execute tasks in a sandboxed environment.
youtube-transcribe-skill
feiskyer/claude-code-settings
Extract subtitles/transcripts from YouTube videos. Triggers: "youtube transcript", "extract subtitles", "video captions", "视频字幕", "字幕提取", "YouTube转文字", "提取字幕".
nanobanana-skill
feiskyer/claude-code-settings
Generate or edit images via Google Gemini (nanobanana). This is the DEFAULT image skill — use whenever the user asks to generate, create, or edit an image and does NOT name another provider. Triggers: "nanobanana", "generate image", "create image", "edit image", "图片生成", "生成图片", "AI绘图", "图片编辑". Do NOT use for diagrams (架构图/流程图/时序图) — draw those with Mermaid or code instead.
deep-research
feiskyer/claude-code-settings
Open the skill to read its SKILL.md instructions.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown：查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件，或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.