Skip to content
Back to search

second-brain-skills

SkillWorks with Claude CodeGitHub

A collection of Claude Skills to turn Claude Code into a Second Brain

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/coleam00-second-brain-skills/badge.svg)](/listings/coleam00-second-brain-skills)

HTML

<a href="/listings/coleam00-second-brain-skills"><img src="/api/listings/coleam00-second-brain-skills/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.

1. **For SOPs and documentation**: Use the SOP Creator directly - it works out of the box 2. **For new skills**: Use the Skill Creator to build your own extensions 3. **For MCP integrations**: - Copy `example-mcp-config.json` to `mcp-config.json` and add your API keys - Ask Claude to test the tools and document any gotchas in `CLAUDE.md` 4. **For videos**: - Run `npx create-video@latest` to create a Remotion project - Start the dev server with `npm run dev` - Tell Claude the project path and start prompting 5. **For presentations**: - First, run the Brand & Voice Generator to set up your brand - Or manually copy and configure the template folder in `brands/` - Then generate slides with the PPTX Generator skill

---

*These skills demonstrate that extending Claude Code is straightforward - it's just well-organized context that makes the agent an expert in your specific workflows.*

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 · 480 lines

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

  1. # Claude Code Second Brain Skills
  2. A collection of custom skills that turn Claude Code into a second brain for knowledge work. These skills demonstrate progressive disclosure of context - there's no magic, just structured knowledge that makes Claude hyper-capable for specific tasks.
  3. ## What This Is
  4. Most people think of Claude Code as a tool for writing and debugging code. These skills extend it into a system for capturing and operationalizing knowledge:
  5. - **External integrations** - Connect to MCP servers (Zapier, GitHub, etc.) without context bloat
  6. - **Video creation** - Programmatic videos with Remotion and React
  7. - **Presentations** - Professional slides and LinkedIn carousels with your brand styling
  8. - **Documentation** - Runbooks, SOPs, and technical docs that people actually follow
  9. - **Skill development** - Creating new skills to extend Claude's capabilities further
  10. - **Brand consistency** - Define your voice and visual identity once, use everywhere
  11. The system works through progressive disclosure: Claude only loads detailed instructions when needed, keeping context efficient while maintaining deep expertise for each domain.
  12. ---
  13. ## Brand & Voice Generator
  14. Generate tone-of-voice and brand-system files that power the PPTX Generator and can guide customization of all the other skills. This skill walks you through creating your brand identity, defining your writing voice, and establishing your visual system.
  15. **Core Philosophy**: Your brand and voice should be documented once and reused everywhere. The files this skill creates become the source of truth for all content generation.
  16. <details>
  17. <summary><big>📦 What It Creates</big></summary>
  18. | File | Purpose | Used By |
  19. |------|---------|---------|
  20. | `brand.json` | Colors, fonts, assets | PPTX Generator |
  21. | `config.json` | Output settings | PPTX Generator |
  22. | `brand-system.md` | Design philosophy & guidelines | All skills |
  23. | `tone-of-voice.md` | Writing voice & personality | PPTX content, SOPs |
  24. </details>
  25. <details>
  26. <summary><big>🔄 Process Overview</big></summary>
  27. 1. **Gather Brand Basics** - Name, description, primary use case
  28. 2. **Define Colors** - 10 color values for the complete system
  29. 3. **Define Typography** - Heading, body, and code fonts
  30. 4. **Define Assets** - Logo and icon paths
  31. 5. **Discover Voice** - Personality, vocabulary, sentence patterns
  32. 6. **Create Design Philosophy** - Core principles and signature elements
  33. 7. **Generate Files** - Create all four files with gathered information
  34. </details>
  35. <details>
  36. <summary><big>🎭 Voice Templates Included</big></summary>
  37. The skill includes 5 example voice configurations to help you discover your own:
  38. - **Technical Educator** - Enthusiastic expert who teaches by showing
  39. - **Calm Authority** - Confident and measured, lets expertise speak through specifics
  40. - **Builder's Perspective** - Developer-to-developer, unfiltered opinions backed by code
  41. - **Approachable Expert** - Makes the complex accessible without dumbing it down
  42. - **Contrarian Thinker** - Challenges conventional wisdom with evidence
  43. </details>
  44. <br/>
  45. **Triggers**: "help me create a brand system", "generate my tone of voice", "set up my brand for presentations", "create brand files"
  46. ---
  47. ## Skills Overview
  48. ### MCP Client
  49. Connect Claude Code to external MCP servers (Zapier, GitHub, Sequential Thinking, etc.) with progressive disclosure - tool schemas load on-demand instead of bloating your context window.
  50. **Core Philosophy**: MCP servers expose thousands of tokens worth of tool definitions. This skill wraps them as a lightweight client, loading only what you need when you need it.
  51. <details>
  52. <summary><big>🔧 Setup: Create Your Config</big></summary>
  53. **Step 1:** Copy the example config to create your own:
  54. ```bash
  55. cp .claude/skills/mcp-client/references/example-mcp-config.json \
  56. .claude/skills/mcp-client/references/mcp-config.json
  57. ```
  58. **Step 2:** Edit `mcp-config.json` with your API keys and servers.
  59. The config format is identical to Claude Desktop's MCP config:
  60. ```json
  61. {
  62. "mcpServers": {
  63. "zapier": {
  64. "url": "https://mcp.zapier.com/api/v1/connect",
  65. "api_key": "YOUR_API_KEY_HERE"
  66. },
  67. "sequential-thinking": {
  68. "command": "npx",
  69. "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]
  70. }
  71. }
  72. }
  73. ```
  74. **Transport types:**
  75. - `url` + `api_key` → Remote server with Bearer auth (Zapier)
  76. - `command` + `args` → Local stdio server (npx, python, docker)
  77. - `url` ending in `/sse` → SSE transport
  78. - `url` ending in `/mcp` → Streamable HTTP
  79. </details>
  80. <details>
  81. <summary><big>📋 Available Commands (Agent Takes Care of This)</big></summary>
  82. ```bash
  83. # List configured servers
  84. python .claude/skills/mcp-client/scripts/mcp_client.py servers
  85. # List tools from a server (with full schemas)
  86. python .claude/skills/mcp-client/scripts/mcp_client.py tools zapier
  87. # Call a tool
  88. python .claude/skills/mcp-client/scripts/mcp_client.py call zapier <tool_name> '{"param": "value"}'
  89. ```
  90. </details>
  91. <details>
  92. <summary><big>📝 Document Tool Gotchas in CLAUDE.md</big></summary>
  93. **Important:** After setting up MCP servers, ask Claude to test each tool and document any quirks. This saves time on future calls.
  94. Add a section to your project's `CLAUDE.md` (or create one) - example:
  95. ```markdown
  96. ## MCP Tool Notes
  97. ### Zapier
  98. - `send_gmail_email`: The `to` field must be a single email, not an array
  99. - `create_notion_page`: Requires `database_id`, not `page_id`
  100. - Rate limit: 2 Zapier tasks per MCP call
  101. ### Sequential Thinking
  102. - Always set `nextThoughtNeeded: true` until final thought
  103. - `totalThoughts` is advisory, can be adjusted mid-process
  104. ```
  105. **Why this matters:** MCP tools often have undocumented argument requirements or behaviors. Testing once and documenting saves context and prevents repeated errors.
  106. **Workflow:**
  107. 1. Connect a new MCP server
  108. 2. Ask Claude: "List all tools from [server] and test each one with sample inputs"
  109. 3. Document any failures, required formats, or gotchas in CLAUDE.md
  110. 4. Claude will reference these notes on future calls
  111. </details>
  112. <br/>
  113. **Example Triggers**: "connect to Zapier", "use MCP server", "list MCP tools", "call Zapier action", or any MCP server interaction
  114. ---
  115. ### PPTX Generator
  116. Generate professional, on-brand presentation slides and LinkedIn carousels using python-pptx.
  117. > **Credit**: This skill was originally created by Rasmus and is [maintained here](https://github.com/Wirasm/presentation-slides-skill). The version here has been adapted with brand-specific configurations.
  118. <details>
  119. <summary><big>🎛️ Three Operating Modes</big></summary>
  120. 1. **Slide Generation** - Create 16:9 presentations with brand styling
  121. 2. **Carousel Generation** - Create square 1:1 LinkedIn carousels (exports to PDF)
  122. 3. **Layout Management** - Create, edit, and improve cookbook layouts
  123. </details>
  124. <details>
  125. <summary><big>✨ Key Features</big></summary>
  126. - 16 slide layout templates in the cookbook (title, content, stats, two-column, multi-card, floating-cards, circular-hero, quote, chart, code, and more)
  127. - 5 carousel-specific layouts (hook, single-point, numbered-point, quote, CTA)
  128. - Brand system with colors, fonts, and assets
  129. - Batch generation (max 5 slides at a time) for reliability
  130. - Variety enforcement rules to prevent repetitive layouts
  131. </details>
  132. <details>
  133. <summary><big>💡 Critical Concept</big></summary>
  134. **Visual-first layout selection** - content-slide is the LAST RESORT, not the default.
  135. The skill includes a decision tree to transform bullets into visual layouts:
  136. - 3-5 equal items → multi-card-slide
  137. - 2-4 big numbers → stats-slide
  138. - Comparing two things → two-column-slide
  139. - Central concept with surrounding items → circular-hero-slide
  140. - Powerful quote → quote-slide
  141. Only use content-slide when none of the visual layouts fit.
  142. </details>
  143. <br/>
  144. **Triggers**: Requests for slides, presentations, carousels, PPTX, or layouts with a brand name
  145. ---
  146. ### SOP Creator
  147. Create runbooks, playbooks, and technical documentation that people actually follow.
  148. **Core Philosophy**: Nobody reads 50-page docs. Make it scannable, actionable, and impossible to misunderstand.
  149. <details>
  150. <summary><big>📂 Document Types</big></summary>
  151. - **Tech/Engineering**: Runbook, Deployment Playbook, Troubleshooting Guide, How-To, ADR
  152. - **Operations/Business**: Process SOP, Checklist, Decision Tree, Handoff Doc
  153. - **Content/Creative**: Production Workflow, Review Process, Publishing Checklist
  154. - **General**: Standard SOP, Quick Reference, Onboarding Guide
  155. </details>
  156. <details>
  157. <summary><big>🏗️ Universal Structure</big></summary>
  158. 1. Definition of Done (checklist - most important, put near the top)
  159. 2. When to Use This
  160. 3. Prerequisites
  161. 4. The Process (numbered steps)
  162. 5. Verify Completion
  163. 6. When Things Go Wrong
  164. 7. Questions?
  165. </details>
  166. <details>
  167. <summary><big>📏 Writing Rules</big></summary>
  168. - Be specific (numbers, names, thresholds - not "as needed" or "regularly")
  169. - Action-first steps (verbs, not descriptions)
  170. - Warnings come first (before the dangerous step, not after)
  171. - Clear decision points (if X, then Y - not "handle based on priority")
  172. </details>
  173. <br/>
  174. **Triggers**: Requests to document a process, create a runbook, build operational docs, formalize technical procedures
  175. ---
  176. ### Skill Creator
  177. Guide for creating effective skills that extend Claude's capabilities.
  178. **Core Philosophy**: Skills are modular, self-contained packages that transform Claude from a general-purpose agent into a specialized agent. Only add context Claude doesn't already have.
  179. <details>
  180. <summary><big>🎁 What Skills Provide</big></summary>
  181. 1. Specialized workflows - Multi-step procedures for specific domains
  182. 2. Tool integrations - Instructions for working with specific file formats or APIs
  183. 3. Domain expertise - Company-specific knowledge, schemas, business logic
  184. 4. Bundled resources - Scripts, references, and assets for complex tasks
  185. </details>
  186. <details>
  187. <summary><big>🧭 Core Principles</big></summary>
  188. - **Concise is Key** - Only add context Claude doesn't already have
  189. - **Set Appropriate Degrees of Freedom** - Match specificity to task fragility
  190. - **Progressive Disclosure** - Metadata always in context, body when triggered, resources as needed
  191. </details>
  192. <details>
  193. <summary><big>🗂️ Skill Anatomy</big></summary>
  194. ```
  195. skill-name/
  196. ├── SKILL.md (required)
  197. │ ├── YAML frontmatter (name, description)
  198. │ └── Markdown instructions
  199. └── Bundled Resources (optional)
  200. ├── scripts/ - Executable code
  201. ├── references/ - Documentation loaded as needed
  202. └── assets/ - Files used in output
  203. ```
  204. </details>
  205. <details>
  206. <summary><big>🔄 Creation Process</big></summary>
  207. 1. Understand with concrete examples
  208. 2. Plan reusable contents
  209. 3. Initialize (run init_skill.py)
  210. 4. Edit and implement
  211. 5. Package (run package_skill.py)
  212. 6. Iterate based on real usage
  213. </details>
  214. **Triggers**: Requests to create or update skills that extend Claude's capabilities
  215. ---
  216. ### Remotion Video Creator
  217. Create programmatic videos using React with [Remotion](https://remotion.dev). This skill gives Claude expert knowledge of the Remotion framework - animations, compositions, assets, captions, and more.
  218. > **Credit**: This skill is from the official [remotion-dev/skills](https://github.com/remotion-dev/skills) repository by Jonny Burger and the Remotion team.
  219. **Core Philosophy**: Videos are React components. Claude writes the code, you see it render in real-time, then export to MP4/WebM.
  220. <details>
  221. <summary><big>🚀 Setup: Create a Remotion Project</big></summary>
  222. **Step 1:** Create a new Remotion project:
  223. ```bash
  224. npx create-video@latest
  225. ```
  226. When prompted, select:
  227. - **Empty** template
  228. - **Enable TailwindCSS** (recommended)
  229. - **Install Skills** (this adds the Remotion skill automatically)
  230. **Step 2:** Start the development server:
  231. ```bash
  232. cd my-video
  233. npm install
  234. npm run dev
  235. ```
  236. This opens a browser preview where you'll see your video render in real-time.
  237. **Step 3:** Point Claude to your project:
  238. ```
  239. "Edit my Remotion project at /path/to/my-video"
  240. ```
  241. Claude will read the project structure and edit the React components in `src/`.
  242. </details>
  243. <details>
  244. <summary><big>🎬 What You Can Create</big></summary>
  245. The skill includes 28 modular rules covering:
  246. - **Animations** - Interpolation, springs, easing curves
  247. - **Compositions** - Multi-scene videos, dynamic duration
  248. - **Assets** - Images, videos, audio, fonts, GIFs, Lottie
  249. - **Text** - Typewriter effects, word highlights, measuring text
  250. - **Captions** - TikTok-style captions, SRT import, transcription
  251. - **Charts** - Animated bar charts, data visualization
  252. - **3D** - Three.js and React Three Fiber integration
  253. - **Transitions** - Scene transitions, sequencing patterns
  254. - **Maps** - Animated Mapbox maps
  255. </details>
  256. <details>
  257. <summary><big>💡 Tips for Prompting</big></summary>
  258. **Good prompts** describe what can be drawn in a web interface:
  259. - "Create a 10-second intro with my logo fading in, then text typing out"
  260. - "Add a bar chart that animates the values from 0 to their final state"
  261. - "Make the title bounce in with a spring animation"
  262. **Don't** asking Claude to produce an entire video - one composition at a time is the way to go.
  263. </details>
  264. <br/>
  265. **Triggers**: Mentions of "Remotion", paths containing `remotion-videos/`, files like `remotion.config.ts`, or requests for animated React video content
  266. ---
  267. ## Customization Guide
  268. These skills work out of the box, but some contain brand-specific configurations you'll want to customize for your own use.
  269. ### What Needs Customization
  270. | Skill | Customization Required | Effort |
  271. |-------|------------------------|--------|
  272. | **SOP Creator** | Works as-is | None |
  273. | **Skill Creator** | Works as-is | None |
  274. | **Remotion** | Create project externally | Low |
  275. | **MCP Client** | Create config + add API keys | Low |
  276. | **PPTX Generator** | Brand system setup required | Medium |
  277. <details>
  278. <summary><big>🟢 No Effort: SOP Creator & Skill Creator</big></summary>
  279. These skills focus on universal principles and workflows that work for anyone. Use them immediately without any configuration.
  280. </details>
  281. <details>
  282. <summary><big>🟡 Low Effort: Remotion</big></summary>
  283. 1. Run `npx create-video@latest` to create a Remotion project
  284. 2. Select Empty template + TailwindCSS + Install Skills
  285. 3. Start `npm run dev` and tell Claude the project path
  286. The skill provides domain knowledge - the project itself lives outside this repo.
  287. </details>
  288. <details>
  289. <summary><big>🟡 Low Effort: MCP Client</big></summary>
  290. 1. Copy `example-mcp-config.json` to `mcp-config.json`
  291. 2. Add your API keys (Zapier, GitHub tokens, etc.)
  292. 3. Test each server's tools and document gotchas in your `CLAUDE.md`
  293. The config format matches Claude Desktop, so you can reuse existing configs.
  294. </details>
  295. <details>
  296. <summary><big>🟡 Medium Effort: PPTX Generator</big></summary>
  297. This skill requires a complete brand setup before generating slides. Use the **Brand & Voice Generator** skill to create these files interactively, or manually copy from the template folder.
  298. **Required files** (in `brands/your-brand-name/`):
  299. 1. **`brand.json`** - Colors (10 values), fonts (3), and asset paths
  300. 2. **`config.json`** - Output directory, batch size, file naming
  301. 3. **`brand-system.md`** - Design philosophy, color rationale, typography rules, signature elements
  302. 4. **`tone-of-voice.md`** - Voice character, vocabulary patterns, do's and don'ts, example phrases
  303. **Setup steps**:
  304. 1. Run the Brand & Voice Generator skill, OR
  305. 2. Copy `brands/template/` to `brands/your-brand-name/`
  306. 3. Replace all `REPLACE` placeholders in each file
  307. 4. Add your logo to `brands/your-brand-name/assets/`
  308. 5. Test by generating a simple presentation
  309. See `brands/dynamous/` for a complete example of a configured brand.
  310. </details>
  311. ---
  312. ## Quick Start
  313. 1. **For SOPs and documentation**: Use the SOP Creator directly - it works out of the box
  314. 2. **For new skills**: Use the Skill Creator to build your own extensions
  315. 3. **For MCP integrations**:
  316. - Copy `example-mcp-config.json` to `mcp-config.json` and add your API keys
  317. - Ask Claude to test the tools and document any gotchas in `CLAUDE.md`
  318. 4. **For videos**:
  319. - Run `npx create-video@latest` to create a Remotion project
  320. - Start the dev server with `npm run dev`
  321. - Tell Claude the project path and start prompting
  322. 5. **For presentations**:
  323. - First, run the Brand & Voice Generator to set up your brand
  324. - Or manually copy and configure the template folder in `brands/`
  325. - Then generate slides with the PPTX Generator skill
  326. ---
  327. *These skills demonstrate that extending Claude Code is straightforward - it's just well-organized context that makes the agent an expert in your specific workflows.*

Ratings and comments

Sign in to rate this skill.

Sign in

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