[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JJE6MKTY09ZMT7VTC4K279":3,"skill-same:01M6JJE6MKTY09ZMT7VTC4K279":63},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6JJE6MKTY09ZMT7VTC4K279","Manifest",null,"Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys or endpoints, troubleshooting plugin connection issues, or verifying the observability pipeline is running.","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\u002Fdevelopment\u002Fmanifest\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"manifest","troubleshooting","api keys","for","keys","connection","endpoints","up","use","install","telemetry","configure","api","pipeline","observability","issues","plugin","2026-11-10 10:12:30",false,"---\nname: Manifest\ndescription: Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys or endpoints, troubleshooting plugin connection issues, or verifying the observability pipeline is running.\n---\n\n# Manifest Setup\n\nSet up real-time observability for your AI agents with the Manifest plugin. Monitors costs, tokens, messages, and performance via OTLP telemetry.\n\n## When to Use This Skill\n\nUse this skill when:\n- Setting up observability or telemetry for an AI agent\n- Connecting an agent to Manifest for cost and performance monitoring\n- Configuring a Manifest API key or custom endpoint\n- Troubleshooting Manifest plugin connection issues\n- Verifying the Manifest observability pipeline is running\n\n## Setup Instructions\n\nFollow these steps **in order**. Do not skip ahead.\n\n### Step 1 — Stop the Gateway\n\nStop the gateway first to avoid hot-reload issues during configuration.\n\n```bash\nclaude gateway stop\n```\n\n### Step 2 — Install the Plugin\n\n```bash\nclaude plugins install manifest\n```\n\nIf it fails, check that the CLI is installed and available in the PATH.\n\n### Step 3 — Get an API Key\n\nAsk the user:\n\n> To connect your agent, you need a Manifest API key:\n>\n> 1. Go to **https:\u002F\u002Fapp.manifest.build** and create an account (or sign in)\n> 2. Click **\"Connect Agent\"** to create a new agent\n> 3. Copy the API key that starts with `mnfst_`\n> 4. Paste it here\n\nWait for a key starting with `mnfst_`. If the key doesn't match, tell the user the format looks incorrect and ask them to try again.\n\n### Step 4 — Configure the Plugin\n\n```bash\nclaude config set plugins.entries.manifest.config.apiKey \"USER_API_KEY\"\n```\n\nReplace `USER_API_KEY` with the actual key the user provided.\n\nIf the user has a custom endpoint (self-hosted):\n\n```bash\nclaude config set plugins.entries.manifest.config.endpoint \"USER_ENDPOINT\"\n```\n\nThe default endpoint (`https:\u002F\u002Fapp.manifest.build\u002Fapi\u002Fv1\u002Fotlp`) is used automatically if none is specified.\n\n### Step 5 — Start the Gateway\n\n```bash\nclaude gateway install\n```\n\n### Step 6 — Verify\n\nWait 3 seconds for the gateway to fully start, then check the logs:\n\n```bash\ngrep \"manifest\" ~\u002F.claude\u002Flogs\u002Fgateway.log | tail -5\n```\n\nLook for:\n\n```\n[manifest] Observability pipeline active\n```\n\nIf it appears, tell the user setup is complete. If not, check the error messages and troubleshoot.\n\n## Troubleshooting\n\n| Error | Fix |\n|-------|-----|\n| Missing apiKey | Re-run Step 4 with the correct key |\n| Invalid apiKey format | Key must start with `mnfst_` |\n| Connection refused | Endpoint is unreachable — check the URL or ask if self-hosting |\n| Duplicate OTel registration | Disable the conflicting built-in plugin: `claude plugins disable diagnostics-otel` |\n\n## Best Practices\n\n- Always stop the gateway before making configuration changes\n- The default endpoint works for most users — only change it if self-hosting\n- API keys always start with `mnfst_` — any other format is invalid\n- Never log or echo the API key in plain text after configuration\n- Check gateway logs first when debugging any plugin issue\n","# Manifest Setup\n\nSet up real-time observability for your AI agents with the Manifest plugin. Monitors costs, tokens, messages, and performance via OTLP telemetry.\n\n## When to Use This Skill\n\nUse this skill when:\n- Setting up observability or telemetry for an AI agent\n- Connecting an agent to Manifest for cost and performance monitoring\n- Configuring a Manifest API key or custom endpoint\n- Troubleshooting Manifest plugin connection issues\n- Verifying the Manifest observability pipeline is running\n\n## Setup Instructions\n\nFollow these steps **in order**. Do not skip ahead.\n\n### Step 1 — Stop the Gateway\n\nStop the gateway first to avoid hot-reload issues during configuration.\n\n```bash\nclaude gateway stop\n```\n\n### Step 2 — Install the Plugin\n\n```bash\nclaude plugins install manifest\n```\n\nIf it fails, check that the CLI is installed and available in the PATH.\n\n### Step 3 — Get an API Key\n\nAsk the user:\n\n> To connect your agent, you need a Manifest API key:\n>\n> 1. Go to **https:\u002F\u002Fapp.manifest.build** and create an account (or sign in)\n> 2. Click **\"Connect Agent\"** to create a new agent\n> 3. Copy the API key that starts with `mnfst_`\n> 4. Paste it here\n\nWait for a key starting with `mnfst_`. If the key doesn't match, tell the user the format looks incorrect and ask them to try again.\n\n### Step 4 — Configure the Plugin\n\n```bash\nclaude config set plugins.entries.manifest.config.apiKey \"USER_API_KEY\"\n```\n\nReplace `USER_API_KEY` with the actual key the user provided.\n\nIf the user has a custom endpoint (self-hosted):\n\n```bash\nclaude config set plugins.entries.manifest.config.endpoint \"USER_ENDPOINT\"\n```\n\nThe default endpoint (`https:\u002F\u002Fapp.manifest.build\u002Fapi\u002Fv1\u002Fotlp`) is used automatically if none is specified.\n\n### Step 5 — Start the Gateway\n\n```bash\nclaude gateway install\n```\n\n### Step 6 — Verify\n\nWait 3 seconds for the gateway to fully start, then check the logs:\n\n```bash\ngrep \"manifest\" ~\u002F.claude\u002Flogs\u002Fgateway.log | tail -5\n```\n\nLook for:\n\n```\n[manifest] Observability pipeline active\n```\n\nIf it appears, tell the user setup is complete. If not, check the error messages and troubleshoot.\n\n## Troubleshooting\n\n| Error | Fix |\n|-------|-----|\n| Missing apiKey | Re-run Step 4 with the correct key |\n| Invalid apiKey format | Key must start with `mnfst_` |\n| Connection refused | Endpoint is unreachable — check the URL or ask if self-hosting |\n| Duplicate OTel registration | Disable the conflicting built-in plugin: `claude plugins disable diagnostics-otel` |\n\n## Best Practices\n\n- Always stop the gateway before making configuration changes\n- The default endpoint works for most users — only change it if self-hosting\n- API keys always start with `mnfst_` — any other format is invalid\n- Never log or echo the API key in plain text after configuration\n- Check gateway logs first when debugging any plugin issue\n",{"name":5,"description":7},"main","34fa6acf794b9a6310d298cbb8fb8c9420a5edcf","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fmanifest",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill Manifest",{"tool":55,"command":56},"bunx","bunx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill Manifest",{"tool":58,"command":59},"pnpm","pnpm dlx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill Manifest","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fmanifest\u002FSKILL.md",true,[],[64,94,115,139,159,185],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":75,"publishedAt":36},"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",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[76,77,78,79,80,81,82,83,84,85,27,86,87,88,89,90,91,92,22,93],"zapier make patterns","patterns","make","zapier","writing","workflow","automation","code","integrations","business","power","complexity","platform","apps","how to","No-Code","which","spawner",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":36},"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",[],[96,101,102,103,104,105,106,107,108,109,110,111,27,112,113,114],"cli","github","commit","pull request","openai","pull","push","flow","open","gh","user","only","stage","github cli",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":36},"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",[121],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[81,82,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,22,93],"Workflow Automation","ai agents","accessibility","workflows","apache","execution","inngest","parallel","orchestrator","resume","n8n","payment","worker","scripts","temporal","with",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":36},"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",[],[146,147,148,149,150,126,151,127,128,152,27,153,154,155,156,157,158,138,22,93],"dev","trigger dev","trigger","design","typescript","async execution","first","async","developer experience","expert","task","background jobs","long",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":36},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000021","资料检索与研究",[169,170,171,138,172,81,173,174,175,176,177,178,27,179,180,181,182,183,184,22],"planning with files","planning","files","with files","storage","tasks","markdown","knowledge","projects","work","manus","structured output","progress","transforms","multi","output",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":195,"publishedAt":36},"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",[191,194],{"categoryNo":192,"categoryName":193,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[81,196,133,197,77,198,199,126,200,174,170,201,31,202,203,204,205,206,207,208],"n8n workflow patterns","workflow patterns","n8n workflow","ai agent","architecture","database","planning workflow","structure","database operations","webhook","processing","http api","scheduled"]