Skip to content
Back to search

skill-from-masters

Stand on the shoulders of giants — Create AI skills built on proven methodologies from domain experts.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/gbsoss--skill-from-masters/badge.svg)](/listings/gbsoss--skill-from-masters)

HTML

<a href="/listings/gbsoss--skill-from-masters"><img src="/api/listings/gbsoss--skill-from-masters/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Option 1: Clone directly (Recommended)

# Navigate to your skills directory
cd ~/.claude/skills  # Claude Code
# or your platform's skills path

# Clone this skill
git clone https://github.com/anthropics/skill-from-masters.git

Option 2: Manual installation

1. Download the `skill-from-masters` folder 2. Place it in your skills directory

Dependency

This skill works with **skill-creator**. Make sure skill-creator is available in your environment.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 248 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Skill From Masters
  2. > **Stand on the shoulders of giants** — Create AI skills built on proven methodologies from domain experts.
  3. A skill that helps you discover and incorporate frameworks, principles, and best practices from recognized masters before generating any new skill. Works with Claude Code, Codex, and other AI agent platforms.
  4. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
  5. ---
  6. ## Why This Skill?
  7. **The hard part of creating a skill isn't the format — it's knowing the best way to do the thing.**
  8. Most professional domains have masters who spent decades figuring out what works:
  9. - Jobs on product, hiring, and marketing
  10. - Bezos on writing (6-pager) and decision-making
  11. - Munger on mental models
  12. - Chris Voss on negotiation
  13. This skill surfaces their methodologies before you write a single line, so your skill embodies world-class expertise from day one.
  14. ## How It Works
  15. ```
  16. 1. You: "I want to create a skill for user interviews"
  17. 2. Skill-from-masters:
  18. ├── Checks local methodology database
  19. ├── Searches web for additional experts
  20. ├── Finds golden examples of great outputs
  21. ├── Identifies common mistakes to avoid
  22. └── Cross-validates across sources
  23. 3. Surfaces experts:
  24. - Rob Fitzpatrick (The Mom Test)
  25. - Steve Portigal (Interviewing Users)
  26. - Nielsen Norman Group best practices
  27. 4. You select which methodologies to incorporate
  28. 5. Extracts actionable principles from primary sources
  29. 6. Hands off to skill-creator to generate the final skill
  30. ```
  31. ## Key Features
  32. | Feature | Description |
  33. |---------|-------------|
  34. | **3-Layer Search** | Local database → Web search for experts → Deep dive on primary sources |
  35. | **Golden Examples** | Finds exemplary outputs to define quality bar |
  36. | **Anti-Patterns** | Searches for common mistakes to encode "don't do this" |
  37. | **Cross-Validation** | Compares multiple experts to find consensus and flag disagreements |
  38. | **Quality Checklist** | Verifies completeness before generating |
  39. ## Methodology Database
  40. The skill includes a curated database covering 15+ domains:
  41. | Domain | Example Experts |
  42. |--------|-----------------|
  43. | Writing | Barbara Minto, William Zinsser, Amazon 6-pager |
  44. | Product | Marty Cagan, Teresa Torres, Gibson Biddle |
  45. | Sales | Neil Rackham (SPIN), Challenger Sale, MEDDIC |
  46. | Hiring | Laszlo Bock, Geoff Smart, Lou Adler |
  47. | User Research | Rob Fitzpatrick, Steve Portigal, JTBD |
  48. | Engineering | Martin Fowler, Robert Martin, Kent Beck |
  49. | Leadership | Kim Scott, Ray Dalio, Andy Grove |
  50. | Negotiation | Chris Voss, Fisher & Ury |
  51. | Startups | Eric Ries, Paul Graham, YC |
  52. | Decision Making | Jeff Bezos, Charlie Munger, Annie Duke |
  53. Plus an **"Oral Tradition"** section for experts who share primarily through talks and interviews (Steve Jobs, Elon Musk, Jensen Huang, Patrick Collison, etc.)
  54. ## Installation
  55. ### Option 1: Clone directly (Recommended)
  56. ```bash
  57. # Navigate to your skills directory
  58. cd ~/.claude/skills # Claude Code
  59. # or your platform's skills path
  60. # Clone this skill
  61. git clone https://github.com/anthropics/skill-from-masters.git
  62. ```
  63. ### Option 2: Manual installation
  64. 1. Download the `skill-from-masters` folder
  65. 2. Place it in your skills directory
  66. ### Dependency
  67. This skill works with **skill-creator**. Make sure skill-creator is available in your environment.
  68. ## Usage
  69. The skill automatically activates when you ask to create a new skill. It runs **before** skill-creator to ensure your skill is built on proven methodologies.
  70. ### Example Session
  71. **You:** "Help me create a skill for writing product requirement documents"
  72. **Skill-from-masters:**
  73. > Let me search for the best methodologies on PRD writing.
  74. >
  75. > *[Searches: "PRD best practices expert", "product requirements document methodology"]*
  76. >
  77. > I found several strong frameworks:
  78. >
  79. > **Product Management:**
  80. > - Marty Cagan: Problem-first PRDs, separating problem space from solution space
  81. > - Teresa Torres: Outcome-focused requirements
  82. >
  83. > **Business Writing:**
  84. > - Barbara Minto: Pyramid Principle - lead with conclusion, MECE structure
  85. > - Amazon: Working backwards, 6-pager narrative format
  86. >
  87. > **Golden Examples Found:**
  88. > - Intercom's public PRD template
  89. > - Linear's product spec format
  90. >
  91. > **Common Mistakes:**
  92. > - Jumping to solutions before defining the problem
  93. > - Writing for engineers instead of for alignment
  94. > - Missing success metrics
  95. >
  96. > Which approaches resonate? Or should I search deeper into any of them?
  97. **You:** "I like Amazon's approach combined with Cagan's problem-first thinking."
  98. **Skill-from-masters:** *[Fetches primary sources on Amazon's methodology, extracts principles, then generates skill via skill-creator]*
  99. ## Skills
  100. This repository contains the following skills:
  101. | Skill | Description |
  102. |-------|-------------|
  103. | **[skill-from-masters](skill-from-masters/SKILL.md)** | Create new skills based on proven methodologies from domain experts. |
  104. | **[search-skill](skills/search-skill/SKILL.md)** | Search for existing skills from trusted marketplaces. |
  105. | **[skill-from-github](skills/skill-from-github/SKILL.md)** | Learn from high-quality GitHub projects and create skills based on that knowledge. |
  106. ### skill-from-masters
  107. When you want to **create a new skill based on expert methodologies**:
  108. - 3-layer search: local database → web experts → primary sources
  109. - Finds golden examples and anti-patterns
  110. - Cross-validates across multiple experts
  111. - Hands off to skill-creator for final generation
  112. **Example:**
  113. ```
  114. You: "Help me create a skill for user interviews"
  115. → Finds: Rob Fitzpatrick (The Mom Test), Steve Portigal, Nielsen Norman Group
  116. → You select which methodologies to incorporate
  117. → Generates skill with those principles encoded
  118. ```
  119. ### search-skill
  120. When you want to **find an existing skill** instead of creating one:
  121. - Searches only 5 trusted sources (no random internet results)
  122. - Tier-based priority: official → curated → aggregators
  123. - Filters out low-quality results (stars < 10, outdated, no SKILL.md)
  124. - Security checks for suspicious code patterns
  125. **Example:**
  126. ```
  127. You: "I need a skill for frontend design, automated testing, and code review"
  128. → Searches: anthropics/skills, ComposioHQ, travisvn, skills.sh, skillsmp.com
  129. → Returns: frontend-design (official), webapp-testing (official), code-review-excellence (26k stars)
  130. ```
  131. ### skill-from-github
  132. When you want to **learn from a GitHub project** and turn that knowledge into a skill:
  133. - Search GitHub for quality projects (stars > 100, actively maintained)
  134. - Present options and wait for your confirmation
  135. - Deep dive into selected project (README, source code, examples)
  136. - Summarize what it learned, then create skill via skill-creator
  137. **Example:**
  138. ```
  139. You: "I want to convert images to ASCII art"
  140. → Searches GitHub, finds: ascii-image-converter (3.1k stars), RASCII (224 stars)
  141. → You select ascii-image-converter
  142. → Learns: brightness-to-character mapping, aspect ratio handling, color techniques
  143. → Creates skill encoding that knowledge (not just wrapping the tool)
  144. ```
  145. **Key difference:** This skill encodes the *knowledge* from projects, so the skill works even without the original tool installed.
  146. ## File Structure
  147. ```
  148. skill-from-masters/
  149. ├── skill-from-masters/
  150. │ ├── SKILL.md # Core skill: create from expert methodologies
  151. │ └── references/
  152. │ ├── methodology-database.md # Curated expert frameworks
  153. │ └── skill-taxonomy.md # 11 skill type categories
  154. ├── skills/
  155. │ ├── search-skill/
  156. │ │ └── SKILL.md # Search existing skills from trusted sources
  157. │ └── skill-from-github/
  158. │ └── SKILL.md # Learn from GitHub projects
  159. ├── README.md
  160. ├── LICENSE
  161. └── .gitignore
  162. ```
  163. ## Quality Checklist
  164. Before finalizing any skill, this skill verifies:
  165. - [ ] Searched beyond the local database
  166. - [ ] Found primary sources, not just summaries
  167. - [ ] Found golden examples of the output
  168. - [ ] Identified common mistakes to avoid
  169. - [ ] Cross-validated across multiple experts
  170. - [ ] Encoded specific, actionable steps (not vague principles)
  171. ## Contributing
  172. Contributions welcome! Especially:
  173. - Adding new domains and experts to the methodology database
  174. - Improving framework descriptions with source links
  175. - Sharing examples of skills created with this approach
  176. Please:
  177. 1. Fork the repository
  178. 2. Create a feature branch
  179. 3. Submit a pull request
  180. ## License
  181. MIT License — feel free to use, modify, and distribute.
  182. ---
  183. **Philosophy:** Quality isn't written. It's selected.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.