skills.rest
billlzzz26
billlzzz26COMMUNITY
Explore all skills by this author →
GitHub

eureka

Capture technical breakthroughs into structured markdown files and update an index.

2|Updated Mar 25, 2026
Search Tags:#templates#documentation#markdown#indexing#patterns#breakthrough#knowledge-management
One-click install
npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill eureka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eureka
Source: https://github.com/billlzzz26/note-taker-convex-ai-convex/tree/main/.agents/skills/eureka
Command: npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill eureka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture technical breakthroughs and transform them into actionable, reusable knowledge assets while the context is fresh.

Core Features & Use Cases

  • Capture Breakthrough: Record the problem, the insight, and the before/after impact to create a trustworthy knowledge artifact.
  • Create Breakthrough File: Generate a structured markdown file at breakthroughs/YYYY-MM-DD-[brief-name].md using a date and concise name, including a standardized template for repeatable capture.
  • Update Index & Patterns: Append the entry to breakthroughs/INDEX.md in reverse chronological order and extract a general reusable pattern for future reuse.

Quick Start

Describe your breakthrough in plain language and I will create the breakthrough file and update the index.

Frequently Asked Questions about eureka

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document technical breakthroughs as reusable knowledge assets?▼

Documenting technical breakthroughs involves capturing the problem, insight, and before/after impact into a structured markdown file with a standardized template, creating a trustworthy knowledge artifact while context is fresh.

What is the best way to index solved technical problems for future reference?▼

Indexing solved technical problems is best handled by appending entries to a chronological INDEX.md file in reverse chronological order, ensuring past breakthroughs remain searchable and accessible for future reference.

Can I extract reusable patterns from hard problems I just solved?▼

You can extract a general reusable pattern from a solved hard problem by documenting the specific insight and transforming it into a generalized pattern for future reuse within your knowledge management system.

How do I structure a markdown file for capturing technical insights?▼

Structuring a markdown file for technical insights requires using a date and concise name format like YYYY-MM-DD-[brief-name].md, containing fields for the problem, the breakthrough insight, and the resulting before/after impact.

Do I need any specific dependencies to create a breakthroughs index?▼

No specific dependencies are required to create a breakthroughs index. You only need to generate structured markdown files and update a chronological index file directly within your existing documentation workflow.

Related Skills

Explore More Content & Communication Skills→
pradyumnasagarpradyumnasagar
6

comm-press-release

Generate press releases from research summaries using the Inverted Pyramid framework.

Community
Intermediate
Khoatran1999Khoatran1999

Meta-Pattern Recognition

Identify repeating patterns across three or more domains and extract abstract forms.

Community
Intermediate
aydinsenturkkaydinsenturkk
3

sw-generate-knowledge

Generate formatted markdown knowledge files from official and community documentation.

Community
Advanced
dallenpyrahdallenpyrah

obsidian-vault

Search, create, and link notes in Obsidian vaults using wikilinks.

Community
Basic