[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76VYG3XRCMACT2JQY7KPMRQ":3,"skill-same:01M76VYG3XRCMACT2JQY7KPMRQ":54},{"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":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M76VYG3XRCMACT2JQY7KPMRQ","ag-second-brain",null,"Use when querying, searching, updating, or adding notes in the Obsidian second brain without fabricating details.","ngxccc\u002Fagent-skills-kit","ngxccc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163379246?v=4","01M758XVG64QK26AGK0WKB26TB","Ngoc Tran","01M758XVHB8J6MHV0YTBVDBXCA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fag-second-brain\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ag-second-brain\ndescription: \"Use when querying, searching, updating, or adding notes in the Obsidian second brain without fabricating details.\"\ntrigger_keywords: second, brain\nlayer: helper\n---\n\n# Second Brain QA & Explainer Skill\n\nThis skill allows the agent to search the local Obsidian second brain using a dedicated script, extract matching notes, and answer user queries with absolute accuracy by citing specific local notes as sources.\n\n## When to Apply\n\n- The user asks for an explanation, summary, or definition of any technical concept, SOP, workflow, or vocabulary term.\n- You need to verify if a specific topic or rule is documented in the second brain before answering.\n- The user explicitly requests searching, updating, adding knowledge, or ducing drafts\u002Finbox notes.\n- The user wants to clean up the inbox or migrate raw notes into structured Atomic Notes.\n\n## How to Use\n\nTo query the second brain for a specific topic, execute the search script:\n\n```bash\nbun \u002Fhome\u002Fngxc\u002Fworkspace\u002Fagent-skills-kit\u002F.agents\u002Fskills\u002Fag-second-brain\u002Fscripts\u002Fsearch_brain.mjs \"\u003Cquery>\"\n```\n\n### Knowledge Modification & Creation Guidelines\n\n1. **Search Before Edit**: Run the search script to check if the concept already exists. Avoid creating duplicate notes for the same concept.\n2. **Updating Existing Notes**:\n   - Maintain the strict 5-part structure (Frontmatter, TL;DR, Core Concept, Concrete Examples, Related Notes).\n   - Run `bun 99_Meta\u002FScripts\u002Fvalidate_notes.mjs \u003Cfile_path>` after editing.\n3. **Creating Inbox Notes**:\n   - Save temporary drafts or raw incoming notes directly to `00_Inbox\u002F\u003Cfilename>.md`. These do not require strict frontmatter or section templates initially.\n4. **Migrating Inbox to Atomic Notes**:\n   - Read the raw note from `00_Inbox\u002F`.\n   - Apply the Litmus Test: If actionable (SOP, scripts, guidelines), place in `30_Resources\u002FMethods\u002F`. If cognitive (theory, definitions), place in `30_Resources\u002FConcepts\u002F` or `30_Resources\u002FTech\u002F`.\n   - Structure the note into the 5-part Atomic Note format.\n   - Add backlinks to relevant MOCs (`000_Tech_MOC`, `000_Concepts_MOC`, or `000_Methods_MOC`) and register the link inside those MOC files.\n   - Run validation script on the new file: `bun 99_Meta\u002FScripts\u002Fvalidate_notes.mjs \u003Cnew_file_path>`.\n   - Once successfully validated, delete the raw note from `00_Inbox\u002F`.\n5. **Creating Workflow Documentation**:\n   - When creating or editing workflow docs in `second-brain\u002FDocs\u002F\u003CTopic>\u002F`, follow the SSOT Workflow Documentation Standard at `process\u002Fdevelopment-protocols\u002Freferences\u002Fworkflow-documentation-standard.md` (via `ag-docs` skill design mode).\n   - Use `docType: feature-workflow` or `docType: infrastructure-workflow`.\n   - Use PascalCase with Underscores file naming: `PascalCase_With_Underscores_Workflow.md` (e.g., `Register_User_Workflow.md`).\n   - Use Codebase Memory MCP graph tools (`search_graph`, `trace_path`, `get_code_snippet`) to extract grounded code symbols and avoid hallucinated routes or DTOs.\n6. **Flashcard Creation & SRS Guidelines**:\n   - **Directory Structure**: Store flashcard files under `50_Flashcards\u002F\u003CDeckName>\u002F` (e.g., `50_Flashcards\u002FBackend\u002F` or `50_Flashcards\u002FVocabulary\u002FCV\u002F`). Yanki automatically derives the Anki deck name from the folder path.\n   - **File Format Constraints**:\n     - **Frontmatter**: Omit standard atomic note tags to skip standard validation. Keep _only_ the `noteId` in the YAML block (e.g., `--- \\n noteId: 12345 \\n ---`) to preserve Anki's review history and avoid duplicate cards.\n     - **No Headings**: Never write `# Title` headings in the body of the markdown, as Yanki renders headings into the Anki card content.\n     - **Separator Spacing**: The thematic break `---` separating front and back content must be surrounded by an empty line both above and below it.\n   - **Supported Yanki Card Syntax**:\n     - **Basic**:\n       ```markdown\n       Front content\n\n       ---\n\n       Back content\n       ```\n     - **Reversed with Extra**: Use a double `---` to create a reversible card (twice the cards). A third `---` defines an \"Extra\" section visible on the back of both generated cards:\n       ```markdown\n       Term \u002F Concept A\n\n       ---\n\n       ---\n\n       Definition \u002F Concept B\n\n       ---\n\n       Extra context shown on both sides\n       ```\n     - **Cloze Deletion**: Hide terms with double tildes `~~`, adding optional `_italics_` inside for hints:\n       ```markdown\n       All will be ~~revealed _hint text_~~.\n       ```\n     - **Advanced Cloze Numbering**: Group clozes to reveal simultaneously by adding a number inside the cloze:\n       ```markdown\n       ~~1 Grouped A~~ and ~~1 Grouped B~~.\n       ```\n     - **Type-in-the-Answer**: Emphasize the last line with `_italics_` to force a spelling text-input check in Anki:\n       ```markdown\n       Spell the term:\n\n       _spelling_\n       ```\n\n### Response Guidelines\n\n1. **Exact Extraction**: Read the source note paths returned by the script and use their content (like `## TL;DR` or `Core Concept`) to answer.\n2. **Mandatory Citations**: Always reference the source note path or link (e.g., `[[Note_Name]]` or `30_Resources\u002FConcepts\u002FPath\u002FNote_Name.md`) at the end of your explanation.\n3. **No Fabrication**: If the script returns `NO_MATCHES_FOUND` or if the matching notes do not contain the answer, you **MUST** explicitly state: \"Kiến thức này không có trong second-brain.\" Do not guess, hallucinate, or use external\u002Fpretrained LLM knowledge to answer the query.\n\n## References\n\n- [Obsidian Second Brain Structure Guidelines](https:\u002F\u002Fobsidian.md\u002F)\n","# Second Brain QA & Explainer Skill\n\nThis skill allows the agent to search the local Obsidian second brain using a dedicated script, extract matching notes, and answer user queries with absolute accuracy by citing specific local notes as sources.\n\n## When to Apply\n\n- The user asks for an explanation, summary, or definition of any technical concept, SOP, workflow, or vocabulary term.\n- You need to verify if a specific topic or rule is documented in the second brain before answering.\n- The user explicitly requests searching, updating, adding knowledge, or ducing drafts\u002Finbox notes.\n- The user wants to clean up the inbox or migrate raw notes into structured Atomic Notes.\n\n## How to Use\n\nTo query the second brain for a specific topic, execute the search script:\n\n```bash\nbun \u002Fhome\u002Fngxc\u002Fworkspace\u002Fagent-skills-kit\u002F.agents\u002Fskills\u002Fag-second-brain\u002Fscripts\u002Fsearch_brain.mjs \"\u003Cquery>\"\n```\n\n### Knowledge Modification & Creation Guidelines\n\n1. **Search Before Edit**: Run the search script to check if the concept already exists. Avoid creating duplicate notes for the same concept.\n2. **Updating Existing Notes**:\n   - Maintain the strict 5-part structure (Frontmatter, TL;DR, Core Concept, Concrete Examples, Related Notes).\n   - Run `bun 99_Meta\u002FScripts\u002Fvalidate_notes.mjs \u003Cfile_path>` after editing.\n3. **Creating Inbox Notes**:\n   - Save temporary drafts or raw incoming notes directly to `00_Inbox\u002F\u003Cfilename>.md`. These do not require strict frontmatter or section templates initially.\n4. **Migrating Inbox to Atomic Notes**:\n   - Read the raw note from `00_Inbox\u002F`.\n   - Apply the Litmus Test: If actionable (SOP, scripts, guidelines), place in `30_Resources\u002FMethods\u002F`. If cognitive (theory, definitions), place in `30_Resources\u002FConcepts\u002F` or `30_Resources\u002FTech\u002F`.\n   - Structure the note into the 5-part Atomic Note format.\n   - Add backlinks to relevant MOCs (`000_Tech_MOC`, `000_Concepts_MOC`, or `000_Methods_MOC`) and register the link inside those MOC files.\n   - Run validation script on the new file: `bun 99_Meta\u002FScripts\u002Fvalidate_notes.mjs \u003Cnew_file_path>`.\n   - Once successfully validated, delete the raw note from `00_Inbox\u002F`.\n5. **Creating Workflow Documentation**:\n   - When creating or editing workflow docs in `second-brain\u002FDocs\u002F\u003CTopic>\u002F`, follow the SSOT Workflow Documentation Standard at `process\u002Fdevelopment-protocols\u002Freferences\u002Fworkflow-documentation-standard.md` (via `ag-docs` skill design mode).\n   - Use `docType: feature-workflow` or `docType: infrastructure-workflow`.\n   - Use PascalCase with Underscores file naming: `PascalCase_With_Underscores_Workflow.md` (e.g., `Register_User_Workflow.md`).\n   - Use Codebase Memory MCP graph tools (`search_graph`, `trace_path`, `get_code_snippet`) to extract grounded code symbols and avoid hallucinated routes or DTOs.\n6. **Flashcard Creation & SRS Guidelines**:\n   - **Directory Structure**: Store flashcard files under `50_Flashcards\u002F\u003CDeckName>\u002F` (e.g., `50_Flashcards\u002FBackend\u002F` or `50_Flashcards\u002FVocabulary\u002FCV\u002F`). Yanki automatically derives the Anki deck name from the folder path.\n   - **File Format Constraints**:\n     - **Frontmatter**: Omit standard atomic note tags to skip standard validation. Keep _only_ the `noteId` in the YAML block (e.g., `--- \\n noteId: 12345 \\n ---`) to preserve Anki's review history and avoid duplicate cards.\n     - **No Headings**: Never write `# Title` headings in the body of the markdown, as Yanki renders headings into the Anki card content.\n     - **Separator Spacing**: The thematic break `---` separating front and back content must be surrounded by an empty line both above and below it.\n   - **Supported Yanki Card Syntax**:\n     - **Basic**:\n       ```markdown\n       Front content\n\n       ---\n\n       Back content\n       ```\n     - **Reversed with Extra**: Use a double `---` to create a reversible card (twice the cards). A third `---` defines an \"Extra\" section visible on the back of both generated cards:\n       ```markdown\n       Term \u002F Concept A\n\n       ---\n\n       ---\n\n       Definition \u002F Concept B\n\n       ---\n\n       Extra context shown on both sides\n       ```\n     - **Cloze Deletion**: Hide terms with double tildes `~~`, adding optional `_italics_` inside for hints:\n       ```markdown\n       All will be ~~revealed _hint text_~~.\n       ```\n     - **Advanced Cloze Numbering**: Group clozes to reveal simultaneously by adding a number inside the cloze:\n       ```markdown\n       ~~1 Grouped A~~ and ~~1 Grouped B~~.\n       ```\n     - **Type-in-the-Answer**: Emphasize the last line with `_italics_` to force a spelling text-input check in Anki:\n       ```markdown\n       Spell the term:\n\n       _spelling_\n       ```\n\n### Response Guidelines\n\n1. **Exact Extraction**: Read the source note paths returned by the script and use their content (like `## TL;DR` or `Core Concept`) to answer.\n2. **Mandatory Citations**: Always reference the source note path or link (e.g., `[[Note_Name]]` or `30_Resources\u002FConcepts\u002FPath\u002FNote_Name.md`) at the end of your explanation.\n3. **No Fabrication**: If the script returns `NO_MATCHES_FOUND` or if the matching notes do not contain the answer, you **MUST** explicitly state: \"Kiến thức này không có trong second-brain.\" Do not guess, hallucinate, or use external\u002Fpretrained LLM knowledge to answer the query.\n\n## References\n\n- [Obsidian Second Brain Structure Guidelines](https:\u002F\u002Fobsidian.md\u002F)\n",{"name":5,"layer":24,"description":7,"trigger_keywords":25},"helper","second, brain","main","1ef0dcd00fe806a8dc4e0b7173b9db967c3ab274",".claude\u002Fskills\u002Fag-second-brain","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit","https:\u002F\u002Fgithub.com\u002Fngxccc","https:\u002F\u002Fngxccc.github.io","Make it work, make it right, make it fast.","2026-08-02 20:59:07",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ngxccc\u002Fagent-skills-kit --skill ag-second-brain",{"tool":40,"command":41},"bunx","bunx skills add ngxccc\u002Fagent-skills-kit --skill ag-second-brain",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ngxccc\u002Fagent-skills-kit --skill ag-second-brain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fag-second-brain\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fsearch_brain.mjs","SCRIPT","脚本",4701,"https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fag-second-brain\u002Fscripts\u002Fsearch_brain.mjs",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M76W3C8X6Q5DS0364KQT7W7A","zustand","Rules and standards for state management using Zustand in React and Next.js. Use when implementing client-side stores, persistence with localStorage, or preventing SSR hydration mismatch.","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002F.curated\u002Fzustand\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M76W39FJGES309VAH7SFWA9Y","zod","Zod v4 schema validation best practices. Use when defining schemas, utilizing safeParse, or customizing error messages.","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002F.curated\u002Fzod\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M76W36HTYA4BR5FKCWMX1RFR","upstash-ratelimit","Rules, standards, and references for rate limiting in serverless environments using Upstash Ratelimit. Use when implementing rate limiting, configuring Upstash Redis, or handling request blocking.","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002F.curated\u002Fupstash-ratelimit\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M76W32H4PS01WFRS7FNPK2G1","ui-design","UI\u002FUX and frontend design best practices guidelines (formerly frontend-design). This skill should be used when writing, reviewing, or designing frontend code to ensure accessibility, performance, and usability. Triggers on tasks involving HTML structure, CSS styling, responsive layouts, form design, animations, or accessibility improvements.","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002F.curated\u002Fui-design\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M76W2YAP6RK8N0EVWFG54VD7","typescript","TypeScript performance, tsconfig, type errors, async patterns — triggered when the user asks to \"optimize TypeScript performance\", \"speed up tsc compilation\", \"configure tsconfig.json\", \"fix type errors\", \"improve async patterns\", or encounters TS errors (TS2322, TS2339, \"is not assignable to\"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002F.curated\u002Ftypescript\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M76W2RMAZNNJQ2HECH3X6ZSH","typescript-refactor","TypeScript and TSX refactoring and modernization guidelines from a principal specialist perspective, current to TypeScript 6.0 and React 19. This skill should be used when refactoring, reviewing, or modernizing TypeScript or React\u002FTSX code for type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving type architecture, narrowing, generics, discriminated unions, error handling, React component and hook typing, or migration to modern TypeScript features (satisfies, using, const type parameters, inferred type predicates, isolatedDeclarations, erasable syntax, import attributes).","https:\u002F\u002Fgithub.com\u002Fngxccc\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002F.curated\u002Ftypescript-refactor\u002FSKILL.md",[],[]]