[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751PKTHE2DA5NDV8RCDGWHE":3,"skill-same:01M751PKTHE2DA5NDV8RCDGWHE":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M751PKTHE2DA5NDV8RCDGWHE","second-brain",null,"Sets up a PARA-based second brain in any notes app (Notion, Obsidian, Apple Notes, Logseq) - Projects, Areas, Resources, Archives buckets, a frictionless universal capture inbox, weekly organizing, wiki-link and map-of-content linking, progressive summarization for recall, and maintenance rituals. Use when someone says \"help me set up a second brain\", \"my notes are a mess and I can never find anything\", \"how do I organize Obsidian with PARA\", or captures ideas but never uses them. Do NOT use for designing the underlying Notion database properties and relations - use notion-database instead - or for a task-management workflow - use gtd-system instead.","SkillMedev\u002Fskills","SkillMedev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298078254?v=4","01M74ZSGTQ918CB0VXW4EG3RMX","SkillMe","01M74ZSGVBT497NA95CBT8JTY4",25,"MIT","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsecond-brain\u002FSKILL.md",[],[],"2026-11-11 18:22:23",false,"---\nname: second-brain\ndescription: Sets up a PARA-based second brain in any notes app (Notion, Obsidian, Apple Notes, Logseq) - Projects, Areas, Resources, Archives buckets, a frictionless universal capture inbox, weekly organizing, wiki-link and map-of-content linking, progressive summarization for recall, and maintenance rituals. Use when someone says \"help me set up a second brain\", \"my notes are a mess and I can never find anything\", \"how do I organize Obsidian with PARA\", or captures ideas but never uses them. Do NOT use for designing the underlying Notion database properties and relations - use notion-database instead - or for a task-management workflow - use gtd-system instead.\nmetadata:\n  title: \"Second Brain\"\n---\n\n# Second Brain\n\nA second brain is an external, trusted system for everything you want to remember\nand act on. This skill sets one up using the PARA method in any notes app\n(Notion, Obsidian, Apple Notes, Logseq).\n\n## The PARA model\n\nOrganize every note into one of four top-level buckets, ordered by actionability:\n\n- **Projects** - short-term efforts with a goal and a deadline (e.g. \"Ship Q3 launch\").\n- **Areas** - ongoing responsibilities with a standard to maintain (e.g. \"Health\", \"Finances\").\n- **Resources** - topics of interest for future reference (e.g. \"Prompt engineering\").\n- **Archives** - inactive items from the other three buckets.\n\nRule: a note lives where you will next *act* on it, not where it topically \"belongs\".\n\n## The four workflows\n\n### 1. Capture\n\nLower friction to near zero. Set up one universal inbox note or quick-capture\nshortcut. Capture anything: ideas, links, quotes, tasks. Do NOT organize at capture\ntime - speed beats structure here.\n\n### 2. Organize (weekly)\n\nOnce a week, empty the inbox. For each item:\n- Is it actionable now? -> attach to a **Project**.\n- Is it an ongoing standard? -> file under an **Area**.\n- Might it be useful later? -> **Resource**.\n- Otherwise -> delete or **Archive**.\n\n### 3. Link\n\nConnect notes so recall works by association, not folders:\n- Add 2-3 `[[wiki-links]]` or relations to related notes when you file something.\n- Maintain a few **index\u002FMOC** (map of content) notes that link out to clusters.\n- Tag sparingly - links beat tags for retrieval.\n\n### 4. Recall (Express)\n\nThe point of the system is output. When starting work:\n- Search the relevant Project\u002FArea note first.\n- Follow links outward to gather supporting Resources.\n- Distill into a working draft. Progressive summarization: bold the best lines,\n  highlight the best of the bold.\n\n## Note template\n\n```\n# \u003CTitle>\nBucket: Projects | Areas | Resources | Archives\nCreated: \u003Cdate>\nLinks: [[related-1]] [[related-2]]\n\n## Summary\n\u003C2-3 sentence why-this-matters>\n\n## Notes\n\u003Ccontent>\n\n## Next action\n\u003Cthe single next step, if any>\n```\n\n## Maintenance rituals\n\n- **Weekly review (20 min):** empty inbox, mark finished projects, archive the dead.\n- **Monthly (10 min):** promote hot Resources, prune stale links.\n\n## Anti-patterns to avoid\n\n- Over-tagging or building deep folder trees - PARA stays flat (4 levels max).\n- Collecting without expressing - capture is only valuable if you later create.\n- Organizing at capture time - it kills capture velocity.\n\n## Quality bar\n\n- Capturing a new thought takes seconds and zero decisions - one inbox, no\n  filing at capture time.\n- Every existing note lands in exactly one PARA bucket, placed by next action,\n  not by topic.\n- Filed notes carry 2-3 outbound links, and each major cluster has an MOC note\n  pointing into it.\n- The weekly and monthly rituals are written down with a trigger (day + time),\n  not left as intentions.\n\n## Deliverable\n\nProduce a working second-brain setup in the user's chosen app: the four PARA\ntop-level buckets created, a universal capture inbox wired to a quick-capture\nentry point, the note template installed, 2-3 starter MOC\u002Findex notes for their\nmain clusters, and a written maintenance checklist (the 20-minute weekly review\nand 10-minute monthly prune) with a scheduled trigger for each.\n","# Second Brain\n\nA second brain is an external, trusted system for everything you want to remember\nand act on. This skill sets one up using the PARA method in any notes app\n(Notion, Obsidian, Apple Notes, Logseq).\n\n## The PARA model\n\nOrganize every note into one of four top-level buckets, ordered by actionability:\n\n- **Projects** - short-term efforts with a goal and a deadline (e.g. \"Ship Q3 launch\").\n- **Areas** - ongoing responsibilities with a standard to maintain (e.g. \"Health\", \"Finances\").\n- **Resources** - topics of interest for future reference (e.g. \"Prompt engineering\").\n- **Archives** - inactive items from the other three buckets.\n\nRule: a note lives where you will next *act* on it, not where it topically \"belongs\".\n\n## The four workflows\n\n### 1. Capture\n\nLower friction to near zero. Set up one universal inbox note or quick-capture\nshortcut. Capture anything: ideas, links, quotes, tasks. Do NOT organize at capture\ntime - speed beats structure here.\n\n### 2. Organize (weekly)\n\nOnce a week, empty the inbox. For each item:\n- Is it actionable now? -> attach to a **Project**.\n- Is it an ongoing standard? -> file under an **Area**.\n- Might it be useful later? -> **Resource**.\n- Otherwise -> delete or **Archive**.\n\n### 3. Link\n\nConnect notes so recall works by association, not folders:\n- Add 2-3 `[[wiki-links]]` or relations to related notes when you file something.\n- Maintain a few **index\u002FMOC** (map of content) notes that link out to clusters.\n- Tag sparingly - links beat tags for retrieval.\n\n### 4. Recall (Express)\n\nThe point of the system is output. When starting work:\n- Search the relevant Project\u002FArea note first.\n- Follow links outward to gather supporting Resources.\n- Distill into a working draft. Progressive summarization: bold the best lines,\n  highlight the best of the bold.\n\n## Note template\n\n```\n# \u003CTitle>\nBucket: Projects | Areas | Resources | Archives\nCreated: \u003Cdate>\nLinks: [[related-1]] [[related-2]]\n\n## Summary\n\u003C2-3 sentence why-this-matters>\n\n## Notes\n\u003Ccontent>\n\n## Next action\n\u003Cthe single next step, if any>\n```\n\n## Maintenance rituals\n\n- **Weekly review (20 min):** empty inbox, mark finished projects, archive the dead.\n- **Monthly (10 min):** promote hot Resources, prune stale links.\n\n## Anti-patterns to avoid\n\n- Over-tagging or building deep folder trees - PARA stays flat (4 levels max).\n- Collecting without expressing - capture is only valuable if you later create.\n- Organizing at capture time - it kills capture velocity.\n\n## Quality bar\n\n- Capturing a new thought takes seconds and zero decisions - one inbox, no\n  filing at capture time.\n- Every existing note lands in exactly one PARA bucket, placed by next action,\n  not by topic.\n- Filed notes carry 2-3 outbound links, and each major cluster has an MOC note\n  pointing into it.\n- The weekly and monthly rituals are written down with a trigger (day + time),\n  not left as intentions.\n\n## Deliverable\n\nProduce a working second-brain setup in the user's chosen app: the four PARA\ntop-level buckets created, a universal capture inbox wired to a quick-capture\nentry point, the note template installed, 2-3 starter MOC\u002Findex notes for their\nmain clusters, and a written maintenance checklist (the 20-minute weekly review\nand 10-minute monthly prune) with a scheduled trigger for each.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Second Brain","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fsecond-brain",3,"https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills","https:\u002F\u002Fskillme.dev","https:\u002F\u002Fgithub.com\u002FSkillMedev","MCP-native catalog of Claude Agent Skills. Browse, recommend, install, and auto-apply skills in chat. Open source, every skill free and clonable on GitHub.","2026-10-14 03:19:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SkillMedev\u002Fskills --skill second-brain",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill second-brain",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill second-brain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsecond-brain\u002FSKILL.md",true,[],[50,60,67,74,81,88],{"skillNo":51,"name":52,"nameZh":53,"description":54,"descriptionZh":55,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":59},"01M75271B256DF3FX2VG5VRYEE","zone-2-cardio-plan","有氧运动计划","Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility\u002Fflexibility routine (use Mobility Routine).","当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练，或提高静息心率、最大摄氧量或耐力时，可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导，不构成医疗建议。请勿用于设计力量或举重训练计划（请使用力量训练计划）、高强度间歇训练 (HIIT) 或循环训练（请使用体能训练和 HIIT 计划），或灵活性\u002F柔韧性训练（请使用灵活性训练计划）。","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzone-2-cardio-plan\u002FSKILL.md",[],[],"2026-11-11 18:27:18",{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":59},"01M7526VP1QBBKYBE17S1WR86Y","youtube-script-writer","Writes retention-engineered long-form YouTube scripts on a hook\u002Fbody\u002Fpayoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says \"script my next video\", \"my retention graph dies at the start\", \"tighten this draft\", or \"outline a video on X\". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-writer\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":59},"01M7526P2T0WKMHDXS4Q58237T","win-back-campaign","Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says \"our users went quiet\", \"design a win-back campaign\", \"how do I re-engage lapsed customers\", \"should we email people who haven't logged in for months\", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":59},"01M7526HF2RCDJ50P93WRZRHVV","wikipedia-style","Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks \"write this like a Wikipedia article\", \"draft a Wikipedia page for this company or person\", \"make this neutral and encyclopedic\", or \"why does my article draft keep getting rejected\". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwikipedia-style\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":59},"01M7526D43CTGRKGKNQ2GB0KVX","whitepapers","Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks \"write a whitepaper on this topic\", \"turn our research into a lead-gen asset\", \"make this credible enough for executives\", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhitepapers\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":59},"01M75268423Y3K50SY5WC2NX2G","white-space-analysis","Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks \"where are the gaps in this market\", \"what's underserved here\", \"where should we play next\", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhite-space-analysis\u002FSKILL.md",[],[]]