[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K320XHEYA5NCXC5FTFB2JS":3,"skill-same:01M6K320XHEYA5NCXC5FTFB2JS":79},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6K320XHEYA5NCXC5FTFB2JS","rudder-worktree-preview-maintainer",null,"Use when starting the current Rudder checkout as a temporary managed local preview with a stable URL, readiness check, logs, stop command, and cleanup path for manual inspection of the current branch or worktree.","Undertone0809\u002Frudder","Undertone0809","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F72488598?v=4","01M6K2XANP3QJEF503JX2C693T","Zeeland","01M6K2XATQXEYF7N2QG8KZVEEY",297,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fagent-skills-bak\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"rudder worktree preview maintainer","worktree","preview","local","for","path","manual","URL","with","checkout","readiness","as","readiness check","stop","use","command","check","branch","logs","cleanup","2026-11-10 10:12:30",false,"---\nname: rudder-worktree-preview-maintainer\ndescription: \"Use when starting the current Rudder checkout as a temporary managed local preview with a stable URL, readiness check, logs, stop command, and cleanup path for manual inspection of the current branch or worktree.\"\n---\n\n# Rudder Worktree Preview Maintainer\n\nRun the current Rudder checkout as a temporary preview so the user can inspect\nthe feature in a browser without leaving a foreground command running.\n\nThis skill is for the common post-implementation hand-off: the branch already\ncontains the work, and the user wants a local URL to test. It is not a PR\ncheckout workflow, it is not a broad process cleanup workflow, and it is not\nthe canonical developer environment for Codex-managed worktrees.\n\nRudder's normal `pnpm dev` entrypoint is the canonical development path. In\nCodex-managed worktrees under `~\u002F.codex\u002Fworktrees\u002F\u003Cid>\u002F\u003Crepo>`, `pnpm dev`\nauto-derives an isolated `RUDDER_HOME`, instance id, server port, embedded\nPostgreSQL port, and worktree branding when no repo-local `.rudder\u002F` config\nexists. Use this preview skill only when the user wants a managed background\npreview handoff with health verification, logs, and a stop command.\n\nPreview readiness is environment proof, not product proof. A healthy URL means\nthe checkout can be opened; it does not prove that a feature, workflow, agent\npath, or UI regression is fixed. When this skill is used inside a lifecycle\nhandoff or review gate, the owning workflow must still exercise the relevant\nroute, command, agent run, or Desktop\u002Fbrowser interaction and report the\nobserved terminal state.\n\n## Use This Skill When\n\n- The user asks to run the current branch or current worktree locally.\n- The user wants to manually test a recently implemented UI or workflow change.\n- The assistant needs to hand off a stable preview URL after implementation\n  without leaving `pnpm dev` in the foreground.\n- The user asks for logs, a stop command, or a temporary preview that can be\n  cleaned up independently.\n- The task is to provide a preview URL, not to package Desktop or publish a\n  release.\n\n## Do Not Use This Skill When\n\n- The user asks to check out or preview a GitHub PR; use\n  `pr-local-preview-maintainer` instead.\n- The user asks only to stop or clean local dev processes; use\n  `stop-rudder-dev-maintainer` instead.\n- The user is asking why Codex worktrees interfere, how normal development\n  should be isolated, or whether `pnpm dev` is using the current worktree. In\n  that case inspect `scripts\u002Fdev-local-env.mjs`, `doc\u002Fengineering\u002FDEVELOPING.md`, and the\n  `\u002Fapi\u002Fhealth` payload for the active dev runtime.\n- The user simply wants to develop inside the current Codex worktree. Use\n  `pnpm dev`, which should auto-isolate Codex-managed worktrees, instead of\n  starting a separate `\u002Ftmp\u002Frudder-worktree-preview` instance.\n- The change needs packaged Desktop verification; follow the Desktop validation\n  workflow in the repo docs.\n- The user wants production-like `pnpm prod` behavior rather than a dev preview.\n\n## Default Workflow\n\n### 1. Inspect the current worktree\n\nStart from the repository root and record the current branch:\n\n```bash\ngit status --short --branch\ngit branch --show-current\n```\n\nDo not switch branches, reset files, or stop unrelated runtimes. A dirty\nworktree is normal after implementation work.\n\n### 2. Choose isolated runtime settings\n\nThe preview is intentionally temporary and may use a different instance than\nthe canonical `pnpm dev` runtime for the same worktree. Tell the user this if\nthey are comparing data between surfaces.\n\nPrefer a branch-derived instance id, a non-default app port, and an isolated\n`RUDDER_HOME` under `\u002Ftmp`:\n\n```text\nRUDDER_INSTANCE_ID=\u003Cbranch-slug>\nPORT=\u003Cfree-port>\nRUDDER_HOME=\u002Ftmp\u002Frudder-worktree-preview\u002F\u003Cbranch-slug>\u002Fhome\n```\n\nUse `3100` only when the user explicitly asks for the default dev runtime and\nthe port is free. Otherwise choose a free port starting near `3310`.\n\nIf the user wants the same data and instance as their normal Codex worktree\ndevelopment surface, do not use this launcher by default. Start or inspect\n`pnpm dev` instead and verify the `\u002Fapi\u002Fhealth` response matches the expected\nworktree-derived instance id.\n\nIf embedded PostgreSQL works, use a free\n`RUDDER_EMBEDDED_POSTGRES_PORT`. If embedded PostgreSQL fails in the local\nenvironment, use a dedicated external database for this preview instead of\nreusing another Rudder instance's database.\n\n### 3. Use the bundled launcher first\n\nFrom the repo root:\n\n```bash\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh\n```\n\nThe launcher:\n\n- derives an instance id from the current branch\n- finds free app and embedded PostgreSQL ports\n- starts `@rudderhq\u002Fserver` with Vite dev middleware\n- uses `tmux` when available, then `launchctl` on macOS\n- waits for `\u002Fapi\u002Fhealth`\n- prints the URL, logs, and stop command\n\nUseful options:\n\n```bash\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --replace\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --port 3312\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --database-url postgres:\u002F\u002Fuser:pass@127.0.0.1:5432\u002Fdbname\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --stop\n```\n\nUse `--replace` only for the same branch-derived preview session. Do not kill\nports or process groups that belong to another Rudder worktree.\n\n### 4. Handle startup failures pragmatically\n\nIf readiness fails, inspect the managed logs before responding:\n\n```bash\ntmux capture-pane -pt rudder-preview-\u003Cinstance-id> -S -180\ntail -180 \u002Ftmp\u002Frudder-worktree-preview\u002F\u003Cinstance-id>\u002F*.log\n```\n\nFix local startup issues that are clearly environmental, such as occupied ports\nor missing dependencies. If embedded PostgreSQL fails, create or use an\nisolated external database and rerun with `--database-url`; do not point the\npreview at the user's main dev data unless they explicitly ask for that.\n\n### 5. Verify readiness\n\nBefore handing off, check:\n\n```bash\ncurl -fsS http:\u002F\u002F127.0.0.1:\u003Cport>\u002Fapi\u002Fhealth\n```\n\nThe `instanceId` in the response should match the preview instance id. If it\ndoes not, the URL may belong to another runtime.\n\nFor visible UI work, also open the URL in a browser when practical. If browser\nautomation is unavailable or hangs, say that clearly and still provide the\nhealth-checked URL.\n\nIf the user asked whether a feature works, do not stop at this readiness check.\nRun or hand back the concrete scenario proof needed for that feature, and label\nthe preview URL as only the environment that made the proof possible.\n\n### 6. Hand off the preview\n\nKeep the response short and concrete:\n\n```text\n当前分支已经跑起来了：\nhttp:\u002F\u002F127.0.0.1:\u003Cport>\n\n实例：\u003Cinstance-id>\n日志：\u003Ctmux attach or log path>\n停止：\u003Cstop command>\nHealth check passed.\n```\n\nMention when the preview uses a non-default port because `3100` is occupied.\nMention when the database is isolated or temporary so the user knows what data\nthey are looking at.\n\n## Cleanup Requests\n\nFor cleanup, stop only the managed preview for the current branch:\n\n```bash\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --stop\n```\n\nVerify the preview port is free afterward. Do not remove worktrees, delete\ndatabases, or stop other Rudder sessions unless the user explicitly asks.\n\n## Judgment Rules\n\n- Isolation matters more than preserving the default port.\n- Do not present this skill as the fix for Codex worktree isolation. That\n  belongs in the default `pnpm dev` environment resolution.\n- Be explicit when this preview uses a temporary `\u002Ftmp` instance that differs\n  from the normal `pnpm dev` instance for the same checkout.\n- A health-checked URL is the minimum hand-off; logs and a stop command make it\n  usable.\n- Do not present preview readiness as review or validation of the changed\n  workflow unless a separate scenario was exercised and reported.\n- Never stop unrelated Rudder sessions just because they occupy `3100`.\n- Do not leave a foreground command running when the user needs a preview after\n  the assistant turn ends; use `tmux` or a user-level managed process.\n- If the task shifts from previewing to fixing a startup bug, say that and keep\n  source edits scoped.\n","# Rudder Worktree Preview Maintainer\n\nRun the current Rudder checkout as a temporary preview so the user can inspect\nthe feature in a browser without leaving a foreground command running.\n\nThis skill is for the common post-implementation hand-off: the branch already\ncontains the work, and the user wants a local URL to test. It is not a PR\ncheckout workflow, it is not a broad process cleanup workflow, and it is not\nthe canonical developer environment for Codex-managed worktrees.\n\nRudder's normal `pnpm dev` entrypoint is the canonical development path. In\nCodex-managed worktrees under `~\u002F.codex\u002Fworktrees\u002F\u003Cid>\u002F\u003Crepo>`, `pnpm dev`\nauto-derives an isolated `RUDDER_HOME`, instance id, server port, embedded\nPostgreSQL port, and worktree branding when no repo-local `.rudder\u002F` config\nexists. Use this preview skill only when the user wants a managed background\npreview handoff with health verification, logs, and a stop command.\n\nPreview readiness is environment proof, not product proof. A healthy URL means\nthe checkout can be opened; it does not prove that a feature, workflow, agent\npath, or UI regression is fixed. When this skill is used inside a lifecycle\nhandoff or review gate, the owning workflow must still exercise the relevant\nroute, command, agent run, or Desktop\u002Fbrowser interaction and report the\nobserved terminal state.\n\n## Use This Skill When\n\n- The user asks to run the current branch or current worktree locally.\n- The user wants to manually test a recently implemented UI or workflow change.\n- The assistant needs to hand off a stable preview URL after implementation\n  without leaving `pnpm dev` in the foreground.\n- The user asks for logs, a stop command, or a temporary preview that can be\n  cleaned up independently.\n- The task is to provide a preview URL, not to package Desktop or publish a\n  release.\n\n## Do Not Use This Skill When\n\n- The user asks to check out or preview a GitHub PR; use\n  `pr-local-preview-maintainer` instead.\n- The user asks only to stop or clean local dev processes; use\n  `stop-rudder-dev-maintainer` instead.\n- The user is asking why Codex worktrees interfere, how normal development\n  should be isolated, or whether `pnpm dev` is using the current worktree. In\n  that case inspect `scripts\u002Fdev-local-env.mjs`, `doc\u002Fengineering\u002FDEVELOPING.md`, and the\n  `\u002Fapi\u002Fhealth` payload for the active dev runtime.\n- The user simply wants to develop inside the current Codex worktree. Use\n  `pnpm dev`, which should auto-isolate Codex-managed worktrees, instead of\n  starting a separate `\u002Ftmp\u002Frudder-worktree-preview` instance.\n- The change needs packaged Desktop verification; follow the Desktop validation\n  workflow in the repo docs.\n- The user wants production-like `pnpm prod` behavior rather than a dev preview.\n\n## Default Workflow\n\n### 1. Inspect the current worktree\n\nStart from the repository root and record the current branch:\n\n```bash\ngit status --short --branch\ngit branch --show-current\n```\n\nDo not switch branches, reset files, or stop unrelated runtimes. A dirty\nworktree is normal after implementation work.\n\n### 2. Choose isolated runtime settings\n\nThe preview is intentionally temporary and may use a different instance than\nthe canonical `pnpm dev` runtime for the same worktree. Tell the user this if\nthey are comparing data between surfaces.\n\nPrefer a branch-derived instance id, a non-default app port, and an isolated\n`RUDDER_HOME` under `\u002Ftmp`:\n\n```text\nRUDDER_INSTANCE_ID=\u003Cbranch-slug>\nPORT=\u003Cfree-port>\nRUDDER_HOME=\u002Ftmp\u002Frudder-worktree-preview\u002F\u003Cbranch-slug>\u002Fhome\n```\n\nUse `3100` only when the user explicitly asks for the default dev runtime and\nthe port is free. Otherwise choose a free port starting near `3310`.\n\nIf the user wants the same data and instance as their normal Codex worktree\ndevelopment surface, do not use this launcher by default. Start or inspect\n`pnpm dev` instead and verify the `\u002Fapi\u002Fhealth` response matches the expected\nworktree-derived instance id.\n\nIf embedded PostgreSQL works, use a free\n`RUDDER_EMBEDDED_POSTGRES_PORT`. If embedded PostgreSQL fails in the local\nenvironment, use a dedicated external database for this preview instead of\nreusing another Rudder instance's database.\n\n### 3. Use the bundled launcher first\n\nFrom the repo root:\n\n```bash\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh\n```\n\nThe launcher:\n\n- derives an instance id from the current branch\n- finds free app and embedded PostgreSQL ports\n- starts `@rudderhq\u002Fserver` with Vite dev middleware\n- uses `tmux` when available, then `launchctl` on macOS\n- waits for `\u002Fapi\u002Fhealth`\n- prints the URL, logs, and stop command\n\nUseful options:\n\n```bash\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --replace\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --port 3312\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --database-url postgres:\u002F\u002Fuser:pass@127.0.0.1:5432\u002Fdbname\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --stop\n```\n\nUse `--replace` only for the same branch-derived preview session. Do not kill\nports or process groups that belong to another Rudder worktree.\n\n### 4. Handle startup failures pragmatically\n\nIf readiness fails, inspect the managed logs before responding:\n\n```bash\ntmux capture-pane -pt rudder-preview-\u003Cinstance-id> -S -180\ntail -180 \u002Ftmp\u002Frudder-worktree-preview\u002F\u003Cinstance-id>\u002F*.log\n```\n\nFix local startup issues that are clearly environmental, such as occupied ports\nor missing dependencies. If embedded PostgreSQL fails, create or use an\nisolated external database and rerun with `--database-url`; do not point the\npreview at the user's main dev data unless they explicitly ask for that.\n\n### 5. Verify readiness\n\nBefore handing off, check:\n\n```bash\ncurl -fsS http:\u002F\u002F127.0.0.1:\u003Cport>\u002Fapi\u002Fhealth\n```\n\nThe `instanceId` in the response should match the preview instance id. If it\ndoes not, the URL may belong to another runtime.\n\nFor visible UI work, also open the URL in a browser when practical. If browser\nautomation is unavailable or hangs, say that clearly and still provide the\nhealth-checked URL.\n\nIf the user asked whether a feature works, do not stop at this readiness check.\nRun or hand back the concrete scenario proof needed for that feature, and label\nthe preview URL as only the environment that made the proof possible.\n\n### 6. Hand off the preview\n\nKeep the response short and concrete:\n\n```text\n当前分支已经跑起来了：\nhttp:\u002F\u002F127.0.0.1:\u003Cport>\n\n实例：\u003Cinstance-id>\n日志：\u003Ctmux attach or log path>\n停止：\u003Cstop command>\nHealth check passed.\n```\n\nMention when the preview uses a non-default port because `3100` is occupied.\nMention when the database is isolated or temporary so the user knows what data\nthey are looking at.\n\n## Cleanup Requests\n\nFor cleanup, stop only the managed preview for the current branch:\n\n```bash\nbash .agents\u002Fskills\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh --stop\n```\n\nVerify the preview port is free afterward. Do not remove worktrees, delete\ndatabases, or stop other Rudder sessions unless the user explicitly asks.\n\n## Judgment Rules\n\n- Isolation matters more than preserving the default port.\n- Do not present this skill as the fix for Codex worktree isolation. That\n  belongs in the default `pnpm dev` environment resolution.\n- Be explicit when this preview uses a temporary `\u002Ftmp` instance that differs\n  from the normal `pnpm dev` instance for the same checkout.\n- A health-checked URL is the minimum hand-off; logs and a stop command make it\n  usable.\n- Do not present preview readiness as review or validation of the changed\n  workflow unless a separate scenario was exercised and reported.\n- Never stop unrelated Rudder sessions just because they occupy `3100`.\n- Do not leave a foreground command running when the user needs a preview after\n  the assistant turn ends; use `tmux` or a user-level managed process.\n- If the task shifts from previewing to fixing a startup bug, say that and keep\n  source edits scoped.\n",{"name":5,"description":7},"main","26d5d68bcbc55caeac1dc6a266d973e8c3831f1c","agent-skills-bak\u002Fmaintainer\u002Frudder-worktree-preview-maintainer",31,"https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder","https:\u002F\u002Frudderhq.dev","https:\u002F\u002Fgithub.com\u002FUndertone0809","Creator of Rudder, Spark Lab. I design SDKs, infra and software for human and the NEW WORLD.","2026-11-08 00:09:15",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Undertone0809\u002Frudder --skill rudder-worktree-preview-maintainer",{"tool":59,"command":60},"bunx","bunx skills add Undertone0809\u002Frudder --skill rudder-worktree-preview-maintainer",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Undertone0809\u002Frudder --skill rudder-worktree-preview-maintainer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fagent-skills-bak\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Frunbook.md","REFERENCE","参考文档",8429,"https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fagent-skills-bak\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Freferences\u002Frunbook.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fstart_current_branch_preview.sh","SCRIPT","脚本",9989,"https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fagent-skills-bak\u002Fmaintainer\u002Frudder-worktree-preview-maintainer\u002Fscripts\u002Fstart_current_branch_preview.sh",[80,93,106,130,159,185],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":39},"01M6K33ZG45BN249F4DZRCCSJN","Source Synthesis","Synthesize evidence into a concise conclusion.","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Ftests\u002Fe2e\u002Ffixtures\u002Fcodex-plugin-research\u002Fskills\u002Fsynthesis\u002FSKILL.md",[],[87,88,89,90,91,92],"Synthesis","source","source synthesis","concise","synthesize","evidence",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":104,"publishedAt":39},"01M6K33XMZXRM31H2SG618C37F","Evidence Research","Gather and cite evidence before reaching a conclusion.","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Ftests\u002Fe2e\u002Ffixtures\u002Fcodex-plugin-research\u002Fskills\u002Fevidence\u002FSKILL.md",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[105,92,95],"research",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":39},"01M6K33RHAPNGPCM2FGPWTZQ8G","deep-research","Conducts enterprise-grade research with multi-source synthesis, citation tracking, and verification. Produces citation-backed reports through a structured pipeline with source credibility scoring, and grounds abstract findings in concrete examples, cases, counterexamples, or mini-scenarios when helpful. Triggers on \"deep research\", \"comprehensive analysis\", \"research report\", \"compare X vs Y\", \"analyze trends\", or \"state of the art\". Not for simple lookups, debugging, or questions answerable with 1-2 searches.","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fserver\u002Fresources\u002Fcommunity-skills\u002Fdeep-research\u002FSKILL.md",[112],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},[114,115,105,116,117,118,89,23,27,119,120,121,122,123,124,125,126,127,128,129],"deep research","deep","state","debugging","triggers","multi","compare","verification","scoring","Art","reports","analyze","analysis","pipeline","Enterprise","examples",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":139,"publishedAt":39},"01M6K33JPMYXHY9E4WR0K9EK0V","visualize","Create safe inline visual explanations in Rudder Chat. Use when asked for a chart, plot, diagram, timeline, comparison, static map, simulator, scenario view, or compact visual that materially improves understanding. Prefer Mermaid for static node-and-edge structures; use Rudder's runtime-neutral HTML\u002FSVG\u002FCSS message envelope for custom geometry. Rudder visuals are declarative and scriptless: convert simulator requests to static scenarios or disclosure-based comparisons and never rely on JavaScript, network access, or external assets.","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fserver\u002Fresources\u002Fbundled-skills\u002Fvisualize\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000009","前端开发",[132,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158],"static","inline","chart","scenario","access","geometry","map","message","compact","back","never","node","mermaid","network","create","diagram","safe","css","markdown",{"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":39},"01M6K339S5PWH9RTZZA71CPD32","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fserver\u002Fresources\u002Fbundled-skills\u002Fskill-creator\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发",[169,170,171,172,173,174,175,176,23,177,178,179,180,33,181,182,126,183,184,154],"skill creator","creator","run evals","performance","variance analysis","existing skill","Existing","accuracy","From Scratch","users","optimize","evals","edit","improve","benchmark","run",{"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":191,"publishedAt":39},"01M6K333T855082YFXZ4FW0SE7","rudder-docs","Use when the user asks how Rudder works; needs current Rudder docs, exact behavior, commands, contracts, APIs, or source evidence; asks to create, hire, or configure Rudder agents; or asks to scaffold, develop, or verify Rudder plugins. For explicit creation requests, verify the current interface before acting within existing authorization. Do not use for greetings, ordinary work merely running inside Rudder, routine actions already clear from the active context and typed tools, non-Rudder plugin work, or general coding and research tasks that do not ask about Rudder.","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fserver\u002Fresources\u002Fbundled-skills\u002Frudder-docs\u002FSKILL.md",[],[192,193,194,88,195,196,197,198,199,200,201,202,203,204,205,206,207,208,154,209],"rudder docs","docs","context","interface","hire","creation","commands","active","do","contracts","ask","work","coding","configure","how","Tools","actions","tasks"]