[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K3145172K0YZJY7NPCMS0V":3,"skill-same:01M6K3145172K0YZJY7NPCMS0V":68},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6K3145172K0YZJY7NPCMS0V","pr-local-preview-maintainer",null,"Use when checking out, running, previewing, reviewing, or validating a GitHub pull request locally in a safe worktree, including PR preview URLs, local screenshots, readiness checks, logs, and cleanup instructions.","Undertone0809\u002Frudder","Undertone0809","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F72488598?v=4","01M6K2XANP3QJEF503JX2C693T","Zeeland","01M6K2XATQXEYF7N2QG8KZVEEY",296,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fagent-skills-bak\u002Fmaintainer\u002Fpr-local-preview-maintainer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"pr","preview","local","pr local preview maintainer","screenshots","safe","github","pull request","cleanup","pull","worktree","logs","instructions","use","readiness","2026-11-10 10:12:30",false,"---\nname: pr-local-preview-maintainer\ndescription: \"Use when checking out, running, previewing, reviewing, or validating a GitHub pull request locally in a safe worktree, including PR preview URLs, local screenshots, readiness checks, logs, and cleanup instructions.\"\n---\n\n# PR Local Preview Maintainer\n\nRun pull requests in a disposable local worktree and give the user a stable\npreview link. The point is to let the user review the PR while protecting their\ncurrent working tree and making UI changes visible.\n\n## Default Workflow\n\n### 1. Preserve the current workspace\n\nStart by checking the repository state:\n\n```bash\ngit status --short --branch\ngh pr view \u003Cnumber> --json number,title,state,headRefName,headRepositoryOwner,url,isCrossRepository\n```\n\nIf the current worktree has local changes, do not run `gh pr checkout` there.\nCreate or reuse a sibling worktree instead. This avoids overwriting unrelated\nwork and keeps the PR preview easy to remove later.\n\nUse a predictable path:\n\n```text\n\u003Crepo-parent>\u002F\u003Crepo-name>-pr-\u003Cnumber>\n```\n\nFor this repository, PR 8 should become:\n\n```text\n\u002FUsers\u002Fzeeland\u002Fprojects\u002Frudder-oss-pr-8\n```\n\nIf the directory already exists, inspect it before reusing it:\n\n```bash\ngit -C \u003Cworktree-path> status --short --branch\ngit -C \u003Cworktree-path> branch --show-current\n```\n\nIf it is dirty, ask only if the dirty changes conflict with the user's goal.\nOtherwise, pick a suffixed path such as `\u003Crepo-name>-pr-\u003Cnumber>-preview`.\n\n### 2. Check out the PR in the worktree\n\nCreate the worktree from the remote base, then check out the PR branch inside it:\n\n```bash\ngit worktree add --detach \u003Cworktree-path> origin\u002Fmain\ngh pr checkout \u003Cnumber> --branch zeelandc\u002Fpr-\u003Cnumber>\n```\n\nIf `main` is not the base branch, use the PR's actual base ref. Prefer a local\nbranch name that makes the preview purpose clear and follows the user's branch\nprefix convention when the repository defines one.\n\nAfter checkout, verify:\n\n```bash\ngit status --short --branch\n```\n\n### 3. Install dependencies only when needed\n\nCheck whether dependencies are present:\n\n```bash\ntest -d node_modules && echo node_modules-present || echo node_modules-missing\n```\n\nIf missing, install them from the worktree:\n\n```bash\npnpm install\n```\n\nReport install warnings only when they affect the preview. Routine peer or bin\nlink warnings can be mentioned briefly.\n\n### 4. Choose isolated runtime settings\n\nBefore starting, inspect occupied ports and existing local runtimes:\n\n```bash\nlsof -nP -iTCP:\u003Ccandidate-port> -sTCP:LISTEN\n```\n\nFor Rudder, prefer:\n\n```bash\nRUDDER_INSTANCE_ID=pr-\u003Cnumber>\nPORT=\u003Cfree-api-port>\nRUDDER_EMBEDDED_POSTGRES_PORT=\u003Cfree-pg-port>\n```\n\nUse `3100` only if it is free and the user clearly wants the default instance.\nIf another Rudder dev runtime is already running, leave it alone and use a\nseparate port and instance ID.\n\nExample:\n\n```bash\nenv RUDDER_INSTANCE_ID=pr-8 PORT=3118 RUDDER_EMBEDDED_POSTGRES_PORT=54358 pnpm dev\n```\n\n### 5. Start the preview so it survives hand-off\n\nUse `tmux` when available. It keeps the preview alive after the assistant turn\nends and gives the user a simple way to inspect logs.\n\n```bash\ntmux new-session -d -s rudder-pr-\u003Cnumber> -c \u003Cworktree-path> \\\n  'env RUDDER_INSTANCE_ID=pr-\u003Cnumber> PORT=\u003Cport> RUDDER_EMBEDDED_POSTGRES_PORT=\u003Cpg-port> pnpm dev'\n```\n\nIf `tmux` is not available, use another managed background process and capture\nlogs to `\u002Ftmp\u002F\u003Crepo-name>-pr-\u003Cnumber>.log`. Do not leave an opaque process\nrunning without telling the user how to stop it.\n\n### 6. Wait for readiness\n\nPoll the health endpoint or the app's equivalent readiness check:\n\n```bash\ncurl -fsS http:\u002F\u002F127.0.0.1:\u003Cport>\u002Fapi\u002Fhealth\n```\n\nIf the app has no health endpoint, use the first meaningful route and check for\na successful response. For frontend-only apps, load the dev server URL and\nconfirm it serves HTML.\n\nWhen startup fails, inspect the session logs before returning:\n\n```bash\ntmux capture-pane -pt rudder-pr-\u003Cnumber> -S -160\n```\n\nFix straightforward startup issues yourself when they are local environment\nproblems, such as missing dependencies or port conflicts. Do not edit PR source\ncode unless the user asked for a fix.\n\n### 7. Decide whether UI screenshots are required\n\nScreenshots are required when any of these are true:\n\n- the PR title, files, or user request mentions UI, layout, pages, components,\n  CSS, design, screenshots, visual review, browser behavior, or interaction\n- changed files live under `ui\u002F`, `desktop\u002F`, frontend route files, component\n  directories, stylesheets, or public assets\n- the user says they want to \"see\" the effect\n\nUse Browser Use for local browser inspection when available. Capture the\nimportant screen or flow after the preview is running. Store temporary\nscreenshots outside the repository, for example:\n\n```text\n\u002Ftmp\u002Frudder-pr-\u003Cnumber>-\u003Cview>.png\n```\n\nFor non-UI backend\u002FAPI PRs, a health check plus a task-specific API smoke check\nis usually enough. If the user still needs to review manually, provide the URL.\n\n### 8. Hand-off format\n\nKeep the final response short and concrete:\n\n```text\nPR \u003Cnumber> is running in \u003Cworktree-path>.\n\nOpen: http:\u002F\u002F127.0.0.1:\u003Cport>\nLogs: tmux attach -t rudder-pr-\u003Cnumber>\nStop: tmux kill-session -t rudder-pr-\u003Cnumber>\n\nHealth check passed: \u003Cbrief status>\nScreenshots: \u003Cpaths or embedded images when UI changed>\n```\n\nIf screenshots were required but could not be captured, say exactly why and\nwhat verification did run.\n\n## Cleanup Requests\n\nWhen the user asks to close, stop, or clean up the preview, stop only the PR\npreview session and verify its port is free:\n\n```bash\ntmux kill-session -t rudder-pr-\u003Cnumber>\nlsof -nP -iTCP:\u003Cport> -sTCP:LISTEN\n```\n\nDo not remove the worktree unless the user explicitly asks for cleanup. If they\ndo ask to remove it, verify the worktree has no uncommitted changes first.\n\n## Safety Notes\n\n- Never use destructive Git commands in the user's main worktree to make a PR\n  checkout succeed.\n- Do not stop unrelated Rudder dev sessions just because the default port is in\n  use; choose an isolated port instead.\n- Keep PR preview data isolated with a dedicated `RUDDER_INSTANCE_ID`.\n- If source edits become necessary, pause and state that the task has shifted\n  from previewing a PR to fixing it.\n","# PR Local Preview Maintainer\n\nRun pull requests in a disposable local worktree and give the user a stable\npreview link. The point is to let the user review the PR while protecting their\ncurrent working tree and making UI changes visible.\n\n## Default Workflow\n\n### 1. Preserve the current workspace\n\nStart by checking the repository state:\n\n```bash\ngit status --short --branch\ngh pr view \u003Cnumber> --json number,title,state,headRefName,headRepositoryOwner,url,isCrossRepository\n```\n\nIf the current worktree has local changes, do not run `gh pr checkout` there.\nCreate or reuse a sibling worktree instead. This avoids overwriting unrelated\nwork and keeps the PR preview easy to remove later.\n\nUse a predictable path:\n\n```text\n\u003Crepo-parent>\u002F\u003Crepo-name>-pr-\u003Cnumber>\n```\n\nFor this repository, PR 8 should become:\n\n```text\n\u002FUsers\u002Fzeeland\u002Fprojects\u002Frudder-oss-pr-8\n```\n\nIf the directory already exists, inspect it before reusing it:\n\n```bash\ngit -C \u003Cworktree-path> status --short --branch\ngit -C \u003Cworktree-path> branch --show-current\n```\n\nIf it is dirty, ask only if the dirty changes conflict with the user's goal.\nOtherwise, pick a suffixed path such as `\u003Crepo-name>-pr-\u003Cnumber>-preview`.\n\n### 2. Check out the PR in the worktree\n\nCreate the worktree from the remote base, then check out the PR branch inside it:\n\n```bash\ngit worktree add --detach \u003Cworktree-path> origin\u002Fmain\ngh pr checkout \u003Cnumber> --branch zeelandc\u002Fpr-\u003Cnumber>\n```\n\nIf `main` is not the base branch, use the PR's actual base ref. Prefer a local\nbranch name that makes the preview purpose clear and follows the user's branch\nprefix convention when the repository defines one.\n\nAfter checkout, verify:\n\n```bash\ngit status --short --branch\n```\n\n### 3. Install dependencies only when needed\n\nCheck whether dependencies are present:\n\n```bash\ntest -d node_modules && echo node_modules-present || echo node_modules-missing\n```\n\nIf missing, install them from the worktree:\n\n```bash\npnpm install\n```\n\nReport install warnings only when they affect the preview. Routine peer or bin\nlink warnings can be mentioned briefly.\n\n### 4. Choose isolated runtime settings\n\nBefore starting, inspect occupied ports and existing local runtimes:\n\n```bash\nlsof -nP -iTCP:\u003Ccandidate-port> -sTCP:LISTEN\n```\n\nFor Rudder, prefer:\n\n```bash\nRUDDER_INSTANCE_ID=pr-\u003Cnumber>\nPORT=\u003Cfree-api-port>\nRUDDER_EMBEDDED_POSTGRES_PORT=\u003Cfree-pg-port>\n```\n\nUse `3100` only if it is free and the user clearly wants the default instance.\nIf another Rudder dev runtime is already running, leave it alone and use a\nseparate port and instance ID.\n\nExample:\n\n```bash\nenv RUDDER_INSTANCE_ID=pr-8 PORT=3118 RUDDER_EMBEDDED_POSTGRES_PORT=54358 pnpm dev\n```\n\n### 5. Start the preview so it survives hand-off\n\nUse `tmux` when available. It keeps the preview alive after the assistant turn\nends and gives the user a simple way to inspect logs.\n\n```bash\ntmux new-session -d -s rudder-pr-\u003Cnumber> -c \u003Cworktree-path> \\\n  'env RUDDER_INSTANCE_ID=pr-\u003Cnumber> PORT=\u003Cport> RUDDER_EMBEDDED_POSTGRES_PORT=\u003Cpg-port> pnpm dev'\n```\n\nIf `tmux` is not available, use another managed background process and capture\nlogs to `\u002Ftmp\u002F\u003Crepo-name>-pr-\u003Cnumber>.log`. Do not leave an opaque process\nrunning without telling the user how to stop it.\n\n### 6. Wait for readiness\n\nPoll the health endpoint or the app's equivalent readiness check:\n\n```bash\ncurl -fsS http:\u002F\u002F127.0.0.1:\u003Cport>\u002Fapi\u002Fhealth\n```\n\nIf the app has no health endpoint, use the first meaningful route and check for\na successful response. For frontend-only apps, load the dev server URL and\nconfirm it serves HTML.\n\nWhen startup fails, inspect the session logs before returning:\n\n```bash\ntmux capture-pane -pt rudder-pr-\u003Cnumber> -S -160\n```\n\nFix straightforward startup issues yourself when they are local environment\nproblems, such as missing dependencies or port conflicts. Do not edit PR source\ncode unless the user asked for a fix.\n\n### 7. Decide whether UI screenshots are required\n\nScreenshots are required when any of these are true:\n\n- the PR title, files, or user request mentions UI, layout, pages, components,\n  CSS, design, screenshots, visual review, browser behavior, or interaction\n- changed files live under `ui\u002F`, `desktop\u002F`, frontend route files, component\n  directories, stylesheets, or public assets\n- the user says they want to \"see\" the effect\n\nUse Browser Use for local browser inspection when available. Capture the\nimportant screen or flow after the preview is running. Store temporary\nscreenshots outside the repository, for example:\n\n```text\n\u002Ftmp\u002Frudder-pr-\u003Cnumber>-\u003Cview>.png\n```\n\nFor non-UI backend\u002FAPI PRs, a health check plus a task-specific API smoke check\nis usually enough. If the user still needs to review manually, provide the URL.\n\n### 8. Hand-off format\n\nKeep the final response short and concrete:\n\n```text\nPR \u003Cnumber> is running in \u003Cworktree-path>.\n\nOpen: http:\u002F\u002F127.0.0.1:\u003Cport>\nLogs: tmux attach -t rudder-pr-\u003Cnumber>\nStop: tmux kill-session -t rudder-pr-\u003Cnumber>\n\nHealth check passed: \u003Cbrief status>\nScreenshots: \u003Cpaths or embedded images when UI changed>\n```\n\nIf screenshots were required but could not be captured, say exactly why and\nwhat verification did run.\n\n## Cleanup Requests\n\nWhen the user asks to close, stop, or clean up the preview, stop only the PR\npreview session and verify its port is free:\n\n```bash\ntmux kill-session -t rudder-pr-\u003Cnumber>\nlsof -nP -iTCP:\u003Cport> -sTCP:LISTEN\n```\n\nDo not remove the worktree unless the user explicitly asks for cleanup. If they\ndo ask to remove it, verify the worktree has no uncommitted changes first.\n\n## Safety Notes\n\n- Never use destructive Git commands in the user's main worktree to make a PR\n  checkout succeed.\n- Do not stop unrelated Rudder dev sessions just because the default port is in\n  use; choose an isolated port instead.\n- Keep PR preview data isolated with a dedicated `RUDDER_INSTANCE_ID`.\n- If source edits become necessary, pause and state that the task has shifted\n  from previewing a PR to fixing it.\n",{"name":5,"description":7},"main","26d5d68bcbc55caeac1dc6a266d973e8c3831f1c","agent-skills-bak\u002Fmaintainer\u002Fpr-local-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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Undertone0809\u002Frudder --skill pr-local-preview-maintainer",{"tool":54,"command":55},"bunx","bunx skills add Undertone0809\u002Frudder --skill pr-local-preview-maintainer",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Undertone0809\u002Frudder --skill pr-local-preview-maintainer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fagent-skills-bak\u002Fmaintainer\u002Fpr-local-preview-maintainer\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Frunbook.md","REFERENCE","参考文档",6170,"https:\u002F\u002Fgithub.com\u002FUndertone0809\u002Frudder\u002Fblob\u002Fmain\u002Fagent-skills-bak\u002Fmaintainer\u002Fpr-local-preview-maintainer\u002Freferences\u002Frunbook.md",[69,82,95,121,149,175],{"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":34},"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",[],[76,77,78,79,80,81],"Synthesis","source","source synthesis","concise","synthesize","evidence",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":93,"publishedAt":34},"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",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[94,81,84],"research",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":102,"publishedAt":34},"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",[101],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[103,104,94,105,106,107,78,108,109,110,111,112,113,114,115,116,117,118,119,120],"deep research","deep","state","debugging","triggers","for","with","multi","compare","verification","scoring","Art","reports","analyze","analysis","pipeline","Enterprise","examples",{"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":130,"publishedAt":34},"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",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000009","前端开发",[123,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,24,147,148],"static","inline","chart","scenario","access","geometry","map","message","compact","back","never","node","mermaid","network","create","diagram","css","markdown",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":34},"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",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000023","Skill与智能体开发",[159,160,161,162,163,164,165,166,108,167,168,169,170,32,171,172,117,173,174,145],"skill creator","creator","run evals","performance","variance analysis","existing skill","Existing","accuracy","From Scratch","users","optimize","evals","edit","improve","benchmark","run",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":34},"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",[],[182,183,184,77,185,186,187,188,189,190,191,192,193,194,195,196,197,198,145,199],"rudder docs","docs","context","interface","hire","creation","commands","active","do","contracts","ask","work","coding","configure","how","Tools","actions","tasks"]