top-one-percent

Solid

Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current paradigms, a complete roadmap or curriculum, deliberate practice and feedback, or a top-1%-level mastery plan. Answer explanation questions completely before offering a curriculum; route explicit mastery goals to an adaptive practice and proof-of-capability system.

AI & Automation 196 stars 7 forks Updated 3 weeks ago MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
76
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Top One Percent Produce unusually clear understanding and evidence-backed mastery. Treat “top one percent” as a direction and a quality standard, not a percentile promise that cannot be measured. ## Follow the Answer-First Contract Match the response to the user's actual intent: - Answer a question as a complete explanation. Do not replace the answer with a roadmap, diagnostic, study plan, or quiz. - Build a mastery system when the user asks to become excellent, requests a curriculum, or wants sustained practice. - Tutor interactively when the user asks for lessons, exercises, assessment, or ongoing coaching. - Combine these only when the combination directly serves the request. If the user asks “Why is X special?”, explain X first; a brief learning path may follow only if useful. Infer the learner's level, goals, and constraints from the request and conversation. State only assumptions that materially affect the answer. Ask at most one high-leverage question when different answers would produce substantially different work; otherwise begin with a sensible default. Personalize examples to the learner's background when known. Do not force every learning-science technique into every response. Retrieval, diagnostics, spacing, and deliberate practice are valuable for building durable capability, but they must not become friction before a user receives the explanation they asked for. ## Route the Request Select the narrowest useful mode. | Mode | Trigger | Primary deliv...

Details

Author
tamdogood
Repository
tamdogood/builder-essential-skills
Created
2 months ago
Last Updated
3 weeks ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

learn

Use this skill when the user wants intellectual understanding — learning how or why something works, not getting a task done or soliciting Claude's judgment. Trigger for: - Explicit learning requests: teach, explain, ELI5, walk me through, quiz me, flashcards, "I'm rusty on"; definitions ("what is X") - Terse concept names implying "help me understand this": "Galois theory," "transformers, from scratch" - Confusion signals: "won't stick," "keep mixing these up," "not getting it" - Learning-path questions: prerequisites, sequencing, what to study before X - Conceptual questions about mechanisms, causes, or dynamics Don't trigger for: - Tasks: coding, writing, calculation, translation, factual lookup, news updates - Personal troubleshooting; resource/textbook recommendations - Claude's evaluative verdict: opinion prompts ("do you think X", "settle this", "honest take", "is X dead / still taken seriously") and interpretive takes ("was X really as harsh as people say")

78 Updated 6 days ago
Razshy
AI & Automation Listed

supertutor

Teach concepts through worked examples, explain-back, and Socratic questions; diagnose misconceptions, build lessons, and verify mastery on novel problems. Includes first-principles engineering. Not production coding or one-off factual lookups.

3 Updated 3 days ago
cskwork
AI & Automation Listed

crash-course

Expert tutor that gets you from zero to working knowledge on any TOPIC fast, grounded in real sources rather than generic filler. Use this whenever the user wants to LEARN, understand, ramp up on, or get up to speed on something and has limited time: a new codebase or project they have been assigned, an unfamiliar technology or framework, a domain concept, an API, a paper, a business area. Triggers on phrases like "help me learn X", "I have N hours to understand X", "teach me X", "get me up to speed on X", "crash course on X", "quiz me on X", "make me a cheat sheet for X", "explain X like I am 5", "I got assigned X and have no context". Runs a timed 4-hour sprint by default, or a single mode on request (cheat sheet, learning ladder, quiz-me, Feynman loop, resource curation). Prefer this over answering a learning request directly, because the value is the structured, interactive, source-grounded teaching loop, not a one-shot dump.

3 Updated today
oleg-koval