[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JKA3DKWRST1GC4K1SJC2FD":3,"skill-same:01M6JKA3DKWRST1GC4K1SJC2FD":70},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6JKA3DKWRST1GC4K1SJC2FD","notion-knowledge-capture",null,"Capture conversations and decisions into structured Notion pages; use when turning chats\u002Fnotes into wiki entries, how-tos, decisions, or FAQs with proper linking.","transaurus\u002Fstaging-davila7-claude-code-templates","transaurus","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F210882017?v=4","01M6JH1R6ZCRXGJCTDP5ZKZBE6","Page Turner Agent","01M6JH1RBBR2P6Y0XWDGM4B0G7",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotion-knowledge-capture\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"notion","knowledge capture","notion knowledge capture","knowledge","capture","linking","conversations","with","tos","pages","structured","entries","use","decisions","wiki","how","notes","2026-11-10 10:12:30",false,"---\nname: notion-knowledge-capture\ndescription: Capture conversations and decisions into structured Notion pages; use when turning chats\u002Fnotes into wiki entries, how-tos, decisions, or FAQs with proper linking.\nmetadata:\n  short-description: Capture conversations into structured Notion pages\n---\n\n# Knowledge Capture\n\nConvert conversations and notes into structured, linkable Notion pages for easy reuse.\n\n## Quick start\n1) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.\n2) Identify the right database\u002Ftemplate in `reference\u002F` (team wiki, how-to, FAQ, decision log, learning, documentation).\n3) Pull any prior context from Notion with `Notion:notion-search` → `Notion:notion-fetch` (existing pages to update\u002Flink).\n4) Draft the page with `Notion:notion-create-pages` using the database's schema; include summary, context, source links, and tags\u002Fowners.\n5) Link from hub pages and related records; update status\u002Fowners with `Notion:notion-update-page` as the source evolves.\n\n## Workflow\n### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:\n1. Add the Notion MCP:\n   - `codex mcp add notion --url https:\u002F\u002Fmcp.notion.com\u002Fmcp`\n2. Enable remote MCP client:\n   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`\n3. Log in with OAuth:\n   - `codex mcp login notion`\n\nAfter successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.\n\n### 1) Define the capture\n- Ask purpose, audience, freshness, and whether this is new or an update.\n- Determine content type: decision, how-to, FAQ, concept\u002Fwiki entry, learning\u002Fnote, documentation page.\n\n### 2) Locate destination\n- Pick the correct database using `reference\u002F*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).\n- If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki\u002Fdocumentation DB.\n\n### 3) Extract and structure\n- Extract facts, decisions, actions, and rationale from the conversation.\n- For decisions, record alternatives, rationale, and outcomes.\n- For how-tos\u002Fdocs, capture steps, pre-reqs, links to assets\u002Fcode, and edge cases.\n- For FAQs, phrase as Q&A with concise answers and links to deeper docs.\n\n### 4) Create\u002Fupdate in Notion\n- Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).\n- Use templates in `reference\u002F` to structure content (section headers, checklists).\n- If updating an existing page, fetch then edit via `Notion:notion-update-page`.\n\n### 5) Link and surface\n- Add relations\u002Fbacklinks to hub pages, related specs\u002Fdocs, and teams.\n- Add a short summary\u002Fchangelog for future readers.\n- If follow-up tasks exist, create tasks in the relevant database and link them.\n\n## References and examples\n- `reference\u002F` — database schemas and templates (e.g., `team-wiki-database.md`, `how-to-guide-database.md`, `faq-database.md`, `decision-log-database.md`, `documentation-database.md`, `learning-database.md`, `database-best-practices.md`).\n- `examples\u002F` — capture patterns in practice (e.g., `decision-capture.md`, `how-to-guide.md`, `conversation-to-faq.md`).\n","# Knowledge Capture\n\nConvert conversations and notes into structured, linkable Notion pages for easy reuse.\n\n## Quick start\n1) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.\n2) Identify the right database\u002Ftemplate in `reference\u002F` (team wiki, how-to, FAQ, decision log, learning, documentation).\n3) Pull any prior context from Notion with `Notion:notion-search` → `Notion:notion-fetch` (existing pages to update\u002Flink).\n4) Draft the page with `Notion:notion-create-pages` using the database's schema; include summary, context, source links, and tags\u002Fowners.\n5) Link from hub pages and related records; update status\u002Fowners with `Notion:notion-update-page` as the source evolves.\n\n## Workflow\n### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:\n1. Add the Notion MCP:\n   - `codex mcp add notion --url https:\u002F\u002Fmcp.notion.com\u002Fmcp`\n2. Enable remote MCP client:\n   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`\n3. Log in with OAuth:\n   - `codex mcp login notion`\n\nAfter successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.\n\n### 1) Define the capture\n- Ask purpose, audience, freshness, and whether this is new or an update.\n- Determine content type: decision, how-to, FAQ, concept\u002Fwiki entry, learning\u002Fnote, documentation page.\n\n### 2) Locate destination\n- Pick the correct database using `reference\u002F*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).\n- If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki\u002Fdocumentation DB.\n\n### 3) Extract and structure\n- Extract facts, decisions, actions, and rationale from the conversation.\n- For decisions, record alternatives, rationale, and outcomes.\n- For how-tos\u002Fdocs, capture steps, pre-reqs, links to assets\u002Fcode, and edge cases.\n- For FAQs, phrase as Q&A with concise answers and links to deeper docs.\n\n### 4) Create\u002Fupdate in Notion\n- Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).\n- Use templates in `reference\u002F` to structure content (section headers, checklists).\n- If updating an existing page, fetch then edit via `Notion:notion-update-page`.\n\n### 5) Link and surface\n- Add relations\u002Fbacklinks to hub pages, related specs\u002Fdocs, and teams.\n- Add a short summary\u002Fchangelog for future readers.\n- If follow-up tasks exist, create tasks in the relevant database and link them.\n\n## References and examples\n- `reference\u002F` — database schemas and templates (e.g., `team-wiki-database.md`, `how-to-guide-database.md`, `faq-database.md`, `decision-log-database.md`, `documentation-database.md`, `learning-database.md`, `database-best-practices.md`).\n- `examples\u002F` — capture patterns in practice (e.g., `decision-capture.md`, `how-to-guide.md`, `conversation-to-faq.md`).\n",{"name":5,"metadata":46,"description":7},{"short-description":47},"Capture conversations into structured Notion pages","main","34fa6acf794b9a6310d298cbb8fb8c9420a5edcf","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotion-knowledge-capture",2,"https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates","https:\u002F\u002Fgithub.com\u002Ftransaurus","Automated works of Page Turner","2026-03-28 10:12:59",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill notion-knowledge-capture",{"tool":62,"command":63},"bunx","bunx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill notion-knowledge-capture",{"tool":65,"command":66},"pnpm","pnpm dlx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill notion-knowledge-capture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotion-knowledge-capture\u002FSKILL.md",true,[],[71,100,121,144,164,187],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":41},"01M6JMRJR3BE0HGWFWDZSB853S","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[81,82,83,84,85,86,87,88,89,90,36,91,92,93,94,95,96,97,98,99],"zapier make patterns","patterns","make","zapier","writing","workflow","automation","code","integrations","business","power","complexity","platform","apps","how to","No-Code","which","for","spawner",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":41},"01M6JMR8YK6SWPCTG1MCQTMN9S","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[102,107,108,109,110,111,112,113,114,115,116,117,36,118,119,120],"cli","github","commit","pull request","openai","pull","push","flow","open","gh","user","only","stage","github cli",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":41},"01M6JMQNFE64ZASQK90HARRXW8","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[127],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[86,87,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,31,98,99],"Workflow Automation","ai agents","accessibility","workflows","apache","execution","inngest","parallel","orchestrator","resume","n8n","payment","worker","scripts","temporal",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":41},"01M6JMQDYJ0XETERPHGDR3EVGN","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[151,152,153,154,155,132,156,133,134,157,36,158,159,160,161,162,163,31,98,99],"dev","trigger dev","trigger","design","typescript","async execution","first","async","developer experience","expert","task","background jobs","long",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":41},"01M6JMQ5J6KK3GSX9FJCWWK6G6","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[170],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,174,31,175,86,176,177,178,27,179,180,36,181,182,183,184,185,186,98],"planning with files","planning","files","with files","storage","tasks","markdown","projects","work","manus","structured output","progress","transforms","multi","output",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":197,"publishedAt":41},"01M6JMPWAT60RXXNEC4V9TRBRS","n8n-workflow-patterns","Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fn8n\u002Fn8n-workflow-patterns\u002FSKILL.md",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[86,198,139,199,82,200,201,132,202,177,173,203,204,205,206,207,208,209,210,211],"n8n workflow patterns","workflow patterns","n8n workflow","ai agent","architecture","database","api","planning workflow","structure","database operations","webhook","processing","http api","scheduled"]