[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-roo-code-triage-sentry":3,"mdc-67wywd-key":37,"related-repo-roo-code-triage-sentry":397,"related-org-roo-code-triage-sentry":499},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"triage-sentry","triage Sentry issues and alerts","Automation skill: Sentry issue triage workflow. Use when a task should periodically scan Roomote Sentry issues, errors, regressions, and alerts via the Sentry MCP, then rank the code or instrumentation follow-up work worth doing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"roo-code","Roo Code","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Froo-code.png","RooCodeInc",[13,17,20,23],{"name":14,"slug":15,"type":16},"Observability","observability","tag",{"name":18,"slug":19,"type":16},"Triage","triage",{"name":21,"slug":22,"type":16},"Sentry","sentry",{"name":24,"slug":25,"type":16},"Debugging","debugging",5,"https:\u002F\u002Fgithub.com\u002FRooCodeInc\u002FRoomote","2026-07-26T05:47:46.334267",null,0,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Your own cloud coding agent. Everything you want from an AI engineering teammate, without building from scratch or paying for a black box.","https:\u002F\u002Fgithub.com\u002FRooCodeInc\u002FRoomote\u002Ftree\u002FHEAD\u002Fpackages\u002Fcloud-agents\u002Fsrc\u002Fserver\u002Fworkflows\u002Fskills\u002Fstandard\u002Ftriage-sentry","---\nname: triage-sentry\nversion: 0.5.0\ndescription: 'Automation skill: Sentry issue triage workflow. Use when a task should periodically scan Roomote Sentry issues, errors, regressions, and alerts via the Sentry MCP, then rank the code or instrumentation follow-up work worth doing.'\ntags:\n  - automation\n---\n\n# Automation\n\nThis is an internal packaged automation skill. It ships with the worker's packaged skill catalog so automations can invoke it outside the Roomote repo.\n\n\u003Crole>\nYou are a Sentry triage specialist for Roomote. Find the Sentry issues materially worth attention today, separate signal from noise, and turn the strongest findings into clear repository-backed follow-up recommendations.\n\u003C\u002Frole>\n\n\u003Cworkflow>\n  \u003Coverview>Run a scheduled-friendly Sentry triage workflow. Use the Sentry MCP as the evidence source, scan the requested window or the last 24 hours by default, and unless the user explicitly narrows or expands the scope, treat the Roomote project set in the target Sentry organization as in-scope by default: `roomote`, `roomote-api`, `roomote-dispatcher`, and `roomote-worker`. Do not include `roomote-cloud` in the default scan. Treat production and preview as separately important, produce a concise prioritized report, and stay read-only.\u003C\u002Foverview>\n\n  \u003Cphase name=\"analysis\">\n    \u003Csteps>\n      \u003Cstep number=\"1\">\n        \u003Ctitle>Initialize task tracking\u003C\u002Ftitle>\n        \u003Cdescription>Create a focused todo list scoped to this Sentry triage run.\u003C\u002Fdescription>\n        \u003Cactions>\n          \u003Caction>Create a todo list covering MCP readiness, Sentry scan, ranking, optional repository cross-check, and reporting.\u003C\u002Faction>\n          \u003Caction>Stay scoped to triage. Do not start implementation work unless the user explicitly asks this task to fix a specific issue.\u003C\u002Faction>\n        \u003C\u002Factions>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"2\">\n        \u003Ctitle>Verify Sentry MCP readiness\u003C\u002Ftitle>\n        \u003Cdescription>Probe the Sentry MCP and report auth or targeting blockers honestly.\u003C\u002Fdescription>\n        \u003Cactions>\n          \u003Caction>Use the Sentry MCP as the primary source for issues, events, stack traces, releases, impacted users, and issue URLs.\u003C\u002Faction>\n          \u003Caction>Probe readiness by verifying the available `mcp__sentry__*` tools and running a narrow read-only issue or project lookup instead of assuming auth and target detection are already correct.\u003C\u002Faction>\n          \u003Caction>If the MCP cannot authenticate, cannot expose the needed Sentry tools, or is scoped to the wrong target, report the exact blocker.\u003C\u002Faction>\n        \u003C\u002Factions>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"3\">\n        \u003Ctitle>Set scan scope\u003C\u002Ftitle>\n        \u003Cdescription>Define the time window, environments, and issue classes to inspect.\u003C\u002Fdescription>\n        \u003Cactions>\n          \u003Caction>Honor an explicit time window from the prompt; otherwise scan the last 24 hours.\u003C\u002Faction>\n          \u003Caction>Honor an explicit project or project-set scope from the prompt when the user names one. Otherwise default to the Roomote project set in the target Sentry organization: `roomote`, `roomote-api`, `roomote-dispatcher`, and `roomote-worker`.\u003C\u002Faction>\n          \u003Caction>Exclude `roomote-cloud` from the default scan unless the user explicitly asks to include it.\u003C\u002Faction>\n          \u003Caction>Inspect issues that are new, regressed, trending, high-frequency, high-user-impact, still unresolved, or materially worse than their recent baseline.\u003C\u002Faction>\n        \u003C\u002Factions>\n      \u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\n  \u003Cphase name=\"triage\">\n    \u003Csteps>\n      \u003Cstep number=\"1\">\n        \u003Ctitle>Collect Sentry evidence\u003C\u002Ftitle>\n        \u003Cdescription>Gather enough evidence to distinguish real problems from noise.\u003C\u002Fdescription>\n        \u003Cactions>\n          \u003Caction>For candidate issues, inspect title, issue ID or URL, short ID, status, first seen, last seen, event count, user count when available, affected release, environment, stack trace summary, tags, and representative event timestamps.\u003C\u002Faction>\n          \u003Caction>Estimate rough evidence counts from Sentry rather than pasting raw events or full stack traces.\u003C\u002Faction>\n          \u003Caction>Use repository inspection only to map a high-confidence issue to a likely subsystem, code path, package, or recent change.\u003C\u002Faction>\n        \u003C\u002Factions>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"2\">\n        \u003Ctitle>Rank the findings\u003C\u002Ftitle>\n        \u003Cdescription>Turn Sentry evidence into a short prioritized recommendation set.\u003C\u002Fdescription>\n        \u003Cactions>\n          \u003Caction>Prioritize by user impact, operational cost, frequency, severity, blast radius, and confidence that the issue is actionable for this workspace.\u003C\u002Faction>\n          \u003Caction>Use the recommendation vocabulary `fix-now | watch | deprioritize | fingerprint | improve-instrumentation`.\u003C\u002Faction>\n          \u003Caction>Keep vendor-side Sentry issue-state changes as prose recommendations only. Do not plan or execute archive, merge, resolve, reopen, or assignment actions from this workflow.\u003C\u002Faction>\n        \u003C\u002Factions>\n      \u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\n  \u003Cphase name=\"report\">\n    \u003Csteps>\n      \u003Cstep number=\"1\">\n        \u003Ctitle>Write the report\u003C\u002Ftitle>\n        \u003Cdescription>Summarize the scan with the highest-signal evidence and next steps.\u003C\u002Fdescription>\n        \u003Cactions>\n          \u003Caction>Start with the scan window, scope, overall risk, and highest-priority finding or no-op result.\u003C\u002Faction>\n          \u003Caction>For each finding include project, environment, why it matters, rough evidence counts, confidence, and one recommendation.\u003C\u002Faction>\n          \u003Caction>If a finding maps clearly to a repository-backed change, say what to change and what to verify first.\u003C\u002Faction>\n          \u003Caction>Call out any setup, auth, or evidence gaps that lowered confidence.\u003C\u002Faction>\n        \u003C\u002Factions>\n      \u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\n\u003Ccompletion_criteria>\n\u003Ccriterion>The workflow used the Sentry MCP as the primary source or reported a clear MCP\u002Fauth\u002Fsetup blocker.\u003C\u002Fcriterion>\n\u003Ccriterion>The scan respected the requested window and project scope.\u003C\u002Fcriterion>\n\u003Ccriterion>The run stayed read-only.\u003C\u002Fcriterion>\n\u003Ccriterion>The final report was concise, prioritized, plain-language, and grounded in evidence.\u003C\u002Fcriterion>\n\u003C\u002Fcompletion_criteria>\n\u003C\u002Fworkflow>\n",{"data":38,"body":42},{"name":4,"version":39,"description":6,"tags":40},"0.5.0",[41],"automation",{"type":43,"children":44},"root",[45,53,59,65],{"type":46,"tag":47,"props":48,"children":49},"element","h1",{"id":41},[50],{"type":51,"value":52},"text","Automation",{"type":46,"tag":54,"props":55,"children":56},"p",{},[57],{"type":51,"value":58},"This is an internal packaged automation skill. It ships with the worker's packaged skill catalog so automations can invoke it outside the Roomote repo.",{"type":46,"tag":60,"props":61,"children":62},"role",{},[63],{"type":51,"value":64},"\nYou are a Sentry triage specialist for Roomote. Find the Sentry issues materially worth attention today, separate signal from noise, and turn the strongest findings into clear repository-backed follow-up recommendations.\n",{"type":46,"tag":66,"props":67,"children":68},"workflow",{},[69,71,77,78,222,223,312,313,369],{"type":51,"value":70},"\n  ",{"type":46,"tag":72,"props":73,"children":74},"overview",{},[75],{"type":51,"value":76},"Run a scheduled-friendly Sentry triage workflow. Use the Sentry MCP as the evidence source, scan the requested window or the last 24 hours by default, and unless the user explicitly narrows or expands the scope, treat the Roomote project set in the target Sentry organization as in-scope by default: `roomote`, `roomote-api`, `roomote-dispatcher`, and `roomote-worker`. Do not include `roomote-cloud` in the default scan. Treat production and preview as separately important, produce a concise prioritized report, and stay read-only.",{"type":51,"value":70},{"type":46,"tag":79,"props":80,"children":82},"phase",{"name":81},"analysis",[83,85,221],{"type":51,"value":84},"\n    ",{"type":46,"tag":86,"props":87,"children":88},"steps",{},[89,91,132,133,173,174,220],{"type":51,"value":90},"\n      ",{"type":46,"tag":92,"props":93,"children":95},"step",{"number":94},"1",[96,98,104,105,111,112,131],{"type":51,"value":97},"\n        ",{"type":46,"tag":99,"props":100,"children":101},"title",{},[102],{"type":51,"value":103},"Initialize task tracking",{"type":51,"value":97},{"type":46,"tag":106,"props":107,"children":108},"description",{},[109],{"type":51,"value":110},"Create a focused todo list scoped to this Sentry triage run.",{"type":51,"value":97},{"type":46,"tag":113,"props":114,"children":115},"actions",{},[116,118,124,125,130],{"type":51,"value":117},"\n          ",{"type":46,"tag":119,"props":120,"children":121},"action",{},[122],{"type":51,"value":123},"Create a todo list covering MCP readiness, Sentry scan, ranking, optional repository cross-check, and reporting.",{"type":51,"value":117},{"type":46,"tag":119,"props":126,"children":127},{},[128],{"type":51,"value":129},"Stay scoped to triage. Do not start implementation work unless the user explicitly asks this task to fix a specific issue.",{"type":51,"value":97},{"type":51,"value":90},{"type":51,"value":90},{"type":46,"tag":92,"props":134,"children":136},{"number":135},"2",[137,138,143,144,149,150,172],{"type":51,"value":97},{"type":46,"tag":99,"props":139,"children":140},{},[141],{"type":51,"value":142},"Verify Sentry MCP readiness",{"type":51,"value":97},{"type":46,"tag":106,"props":145,"children":146},{},[147],{"type":51,"value":148},"Probe the Sentry MCP and report auth or targeting blockers honestly.",{"type":51,"value":97},{"type":46,"tag":113,"props":151,"children":152},{},[153,154,159,160,165,166,171],{"type":51,"value":117},{"type":46,"tag":119,"props":155,"children":156},{},[157],{"type":51,"value":158},"Use the Sentry MCP as the primary source for issues, events, stack traces, releases, impacted users, and issue URLs.",{"type":51,"value":117},{"type":46,"tag":119,"props":161,"children":162},{},[163],{"type":51,"value":164},"Probe readiness by verifying the available `mcp__sentry__*` tools and running a narrow read-only issue or project lookup instead of assuming auth and target detection are already correct.",{"type":51,"value":117},{"type":46,"tag":119,"props":167,"children":168},{},[169],{"type":51,"value":170},"If the MCP cannot authenticate, cannot expose the needed Sentry tools, or is scoped to the wrong target, report the exact blocker.",{"type":51,"value":97},{"type":51,"value":90},{"type":51,"value":90},{"type":46,"tag":92,"props":175,"children":177},{"number":176},"3",[178,179,184,185,190,191,219],{"type":51,"value":97},{"type":46,"tag":99,"props":180,"children":181},{},[182],{"type":51,"value":183},"Set scan scope",{"type":51,"value":97},{"type":46,"tag":106,"props":186,"children":187},{},[188],{"type":51,"value":189},"Define the time window, environments, and issue classes to inspect.",{"type":51,"value":97},{"type":46,"tag":113,"props":192,"children":193},{},[194,195,200,201,206,207,212,213,218],{"type":51,"value":117},{"type":46,"tag":119,"props":196,"children":197},{},[198],{"type":51,"value":199},"Honor an explicit time window from the prompt; otherwise scan the last 24 hours.",{"type":51,"value":117},{"type":46,"tag":119,"props":202,"children":203},{},[204],{"type":51,"value":205},"Honor an explicit project or project-set scope from the prompt when the user names one. Otherwise default to the Roomote project set in the target Sentry organization: `roomote`, `roomote-api`, `roomote-dispatcher`, and `roomote-worker`.",{"type":51,"value":117},{"type":46,"tag":119,"props":208,"children":209},{},[210],{"type":51,"value":211},"Exclude `roomote-cloud` from the default scan unless the user explicitly asks to include it.",{"type":51,"value":117},{"type":46,"tag":119,"props":214,"children":215},{},[216],{"type":51,"value":217},"Inspect issues that are new, regressed, trending, high-frequency, high-user-impact, still unresolved, or materially worse than their recent baseline.",{"type":51,"value":97},{"type":51,"value":90},{"type":51,"value":84},{"type":51,"value":70},{"type":51,"value":70},{"type":46,"tag":79,"props":224,"children":225},{"name":19},[226,227,311],{"type":51,"value":84},{"type":46,"tag":86,"props":228,"children":229},{},[230,231,270,271,310],{"type":51,"value":90},{"type":46,"tag":92,"props":232,"children":233},{"number":94},[234,235,240,241,246,247,269],{"type":51,"value":97},{"type":46,"tag":99,"props":236,"children":237},{},[238],{"type":51,"value":239},"Collect Sentry evidence",{"type":51,"value":97},{"type":46,"tag":106,"props":242,"children":243},{},[244],{"type":51,"value":245},"Gather enough evidence to distinguish real problems from noise.",{"type":51,"value":97},{"type":46,"tag":113,"props":248,"children":249},{},[250,251,256,257,262,263,268],{"type":51,"value":117},{"type":46,"tag":119,"props":252,"children":253},{},[254],{"type":51,"value":255},"For candidate issues, inspect title, issue ID or URL, short ID, status, first seen, last seen, event count, user count when available, affected release, environment, stack trace summary, tags, and representative event timestamps.",{"type":51,"value":117},{"type":46,"tag":119,"props":258,"children":259},{},[260],{"type":51,"value":261},"Estimate rough evidence counts from Sentry rather than pasting raw events or full stack traces.",{"type":51,"value":117},{"type":46,"tag":119,"props":264,"children":265},{},[266],{"type":51,"value":267},"Use repository inspection only to map a high-confidence issue to a likely subsystem, code path, package, or recent change.",{"type":51,"value":97},{"type":51,"value":90},{"type":51,"value":90},{"type":46,"tag":92,"props":272,"children":273},{"number":135},[274,275,280,281,286,287,309],{"type":51,"value":97},{"type":46,"tag":99,"props":276,"children":277},{},[278],{"type":51,"value":279},"Rank the findings",{"type":51,"value":97},{"type":46,"tag":106,"props":282,"children":283},{},[284],{"type":51,"value":285},"Turn Sentry evidence into a short prioritized recommendation set.",{"type":51,"value":97},{"type":46,"tag":113,"props":288,"children":289},{},[290,291,296,297,302,303,308],{"type":51,"value":117},{"type":46,"tag":119,"props":292,"children":293},{},[294],{"type":51,"value":295},"Prioritize by user impact, operational cost, frequency, severity, blast radius, and confidence that the issue is actionable for this workspace.",{"type":51,"value":117},{"type":46,"tag":119,"props":298,"children":299},{},[300],{"type":51,"value":301},"Use the recommendation vocabulary `fix-now | watch | deprioritize | fingerprint | improve-instrumentation`.",{"type":51,"value":117},{"type":46,"tag":119,"props":304,"children":305},{},[306],{"type":51,"value":307},"Keep vendor-side Sentry issue-state changes as prose recommendations only. Do not plan or execute archive, merge, resolve, reopen, or assignment actions from this workflow.",{"type":51,"value":97},{"type":51,"value":90},{"type":51,"value":84},{"type":51,"value":70},{"type":51,"value":70},{"type":46,"tag":79,"props":314,"children":316},{"name":315},"report",[317,318,368],{"type":51,"value":84},{"type":46,"tag":86,"props":319,"children":320},{},[321,322,367],{"type":51,"value":90},{"type":46,"tag":92,"props":323,"children":324},{"number":94},[325,326,331,332,337,338,366],{"type":51,"value":97},{"type":46,"tag":99,"props":327,"children":328},{},[329],{"type":51,"value":330},"Write the report",{"type":51,"value":97},{"type":46,"tag":106,"props":333,"children":334},{},[335],{"type":51,"value":336},"Summarize the scan with the highest-signal evidence and next steps.",{"type":51,"value":97},{"type":46,"tag":113,"props":339,"children":340},{},[341,342,347,348,353,354,359,360,365],{"type":51,"value":117},{"type":46,"tag":119,"props":343,"children":344},{},[345],{"type":51,"value":346},"Start with the scan window, scope, overall risk, and highest-priority finding or no-op result.",{"type":51,"value":117},{"type":46,"tag":119,"props":349,"children":350},{},[351],{"type":51,"value":352},"For each finding include project, environment, why it matters, rough evidence counts, confidence, and one recommendation.",{"type":51,"value":117},{"type":46,"tag":119,"props":355,"children":356},{},[357],{"type":51,"value":358},"If a finding maps clearly to a repository-backed change, say what to change and what to verify first.",{"type":51,"value":117},{"type":46,"tag":119,"props":361,"children":362},{},[363],{"type":51,"value":364},"Call out any setup, auth, or evidence gaps that lowered confidence.",{"type":51,"value":97},{"type":51,"value":90},{"type":51,"value":84},{"type":51,"value":70},{"type":46,"tag":54,"props":370,"children":371},{},[372,374,380,385,390,395],{"type":51,"value":373},"\u003Ccompletion_criteria>\n",{"type":46,"tag":375,"props":376,"children":377},"criterion",{},[378],{"type":51,"value":379},"The workflow used the Sentry MCP as the primary source or reported a clear MCP\u002Fauth\u002Fsetup blocker.",{"type":46,"tag":375,"props":381,"children":382},{},[383],{"type":51,"value":384},"The scan respected the requested window and project scope.",{"type":46,"tag":375,"props":386,"children":387},{},[388],{"type":51,"value":389},"The run stayed read-only.",{"type":46,"tag":375,"props":391,"children":392},{},[393],{"type":51,"value":394},"The final report was concise, prioritized, plain-language, and grounded in evidence.",{"type":51,"value":396},"\n\u003C\u002Fcompletion_criteria>\n",{"items":398,"total":498},[399,415,431,443,457,471,488],{"slug":400,"name":400,"fn":401,"description":402,"org":403,"tags":404,"stars":26,"repoUrl":27,"updatedAt":414},"address-pr-feedback","address unresolved GitHub PR feedback","Focused GitHub PR-feedback workflow for addressing unresolved review threads on the current pull request.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[405,408,411],{"name":406,"slug":407,"type":16},"Code Review","code-review",{"name":409,"slug":410,"type":16},"GitHub","github",{"name":412,"slug":413,"type":16},"Pull Requests","pull-requests","2026-07-19T05:38:26.334008",{"slug":416,"name":416,"fn":417,"description":418,"org":419,"tags":420,"stars":26,"repoUrl":27,"updatedAt":430},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[421,424,427],{"name":422,"slug":423,"type":16},"Browser Automation","browser-automation",{"name":425,"slug":426,"type":16},"CLI","cli",{"name":428,"slug":429,"type":16},"Testing","testing","2026-07-16T06:02:26.045337",{"slug":432,"name":432,"fn":433,"description":434,"org":435,"tags":436,"stars":26,"repoUrl":27,"updatedAt":442},"capture-visual-proof","capture visual proof of browser tasks","Visual-proof orchestrator that decides whether browser proof applies, classifies the proof package, and delegates capture to the hidden proof-runner subagent.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[437,438,439],{"name":52,"slug":41,"type":16},{"name":422,"slug":423,"type":16},{"name":440,"slug":441,"type":16},"Screenshots","screenshots","2026-08-01T05:44:47.369293",{"slug":444,"name":444,"fn":445,"description":446,"org":447,"tags":448,"stars":26,"repoUrl":27,"updatedAt":456},"ci-failure-triage","triage failed CI workflows","Investigate the latest default-branch CI failure in an environment-backed workspace and, when it is real and fixable, fix and open a PR in the same task.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[449,452,453],{"name":450,"slug":451,"type":16},"CI\u002FCD","ci-cd",{"name":24,"slug":25,"type":16},{"name":454,"slug":455,"type":16},"GitHub Actions","github-actions","2026-07-23T05:40:41.726992",{"slug":458,"name":458,"fn":459,"description":460,"org":461,"tags":462,"stars":26,"repoUrl":27,"updatedAt":470},"code-quality-auditor","audit code quality in merged pull requests","Automation skill: review recently merged pull requests for high-confidence code quality issues and submit `act` work items that auto-start follow-up execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[463,466,467],{"name":464,"slug":465,"type":16},"Code Analysis","code-analysis",{"name":406,"slug":407,"type":16},{"name":468,"slug":469,"type":16},"QA","qa","2026-07-26T05:47:47.339721",{"slug":472,"name":472,"fn":473,"description":474,"org":475,"tags":476,"stars":26,"repoUrl":27,"updatedAt":487},"codeql-triage","triage and remediate CodeQL security alerts","Review current open CodeQL \u002F GitHub code-scanning alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start remediation execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[477,478,481,482,483,486],{"name":464,"slug":465,"type":16},{"name":479,"slug":480,"type":16},"CodeQL","codeql",{"name":24,"slug":25,"type":16},{"name":409,"slug":410,"type":16},{"name":484,"slug":485,"type":16},"Security","security",{"name":18,"slug":19,"type":16},"2026-07-29T05:39:37.784486",{"slug":489,"name":489,"fn":490,"description":491,"org":492,"tags":493,"stars":26,"repoUrl":27,"updatedAt":497},"create-draft-pr","create draft pull requests","Draft pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want draft PRs created.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[494,495,496],{"name":52,"slug":41,"type":16},{"name":409,"slug":410,"type":16},{"name":412,"slug":413,"type":16},"2026-07-16T06:00:31.733527",33,{"items":500,"total":498},[501,507,513,519,525,531,540,546,555,567,578,591],{"slug":400,"name":400,"fn":401,"description":402,"org":502,"tags":503,"stars":26,"repoUrl":27,"updatedAt":414},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[504,505,506],{"name":406,"slug":407,"type":16},{"name":409,"slug":410,"type":16},{"name":412,"slug":413,"type":16},{"slug":416,"name":416,"fn":417,"description":418,"org":508,"tags":509,"stars":26,"repoUrl":27,"updatedAt":430},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[510,511,512],{"name":422,"slug":423,"type":16},{"name":425,"slug":426,"type":16},{"name":428,"slug":429,"type":16},{"slug":432,"name":432,"fn":433,"description":434,"org":514,"tags":515,"stars":26,"repoUrl":27,"updatedAt":442},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[516,517,518],{"name":52,"slug":41,"type":16},{"name":422,"slug":423,"type":16},{"name":440,"slug":441,"type":16},{"slug":444,"name":444,"fn":445,"description":446,"org":520,"tags":521,"stars":26,"repoUrl":27,"updatedAt":456},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[522,523,524],{"name":450,"slug":451,"type":16},{"name":24,"slug":25,"type":16},{"name":454,"slug":455,"type":16},{"slug":458,"name":458,"fn":459,"description":460,"org":526,"tags":527,"stars":26,"repoUrl":27,"updatedAt":470},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[528,529,530],{"name":464,"slug":465,"type":16},{"name":406,"slug":407,"type":16},{"name":468,"slug":469,"type":16},{"slug":472,"name":472,"fn":473,"description":474,"org":532,"tags":533,"stars":26,"repoUrl":27,"updatedAt":487},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[534,535,536,537,538,539],{"name":464,"slug":465,"type":16},{"name":479,"slug":480,"type":16},{"name":24,"slug":25,"type":16},{"name":409,"slug":410,"type":16},{"name":484,"slug":485,"type":16},{"name":18,"slug":19,"type":16},{"slug":489,"name":489,"fn":490,"description":491,"org":541,"tags":542,"stars":26,"repoUrl":27,"updatedAt":497},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[543,544,545],{"name":52,"slug":41,"type":16},{"name":409,"slug":410,"type":16},{"name":412,"slug":413,"type":16},{"slug":547,"name":547,"fn":548,"description":549,"org":550,"tags":551,"stars":26,"repoUrl":27,"updatedAt":554},"create-pr","create pull requests for pending changes","Pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want ready-for-review PRs created.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[552,553],{"name":409,"slug":410,"type":16},{"name":412,"slug":413,"type":16},"2026-07-16T06:03:03.397562",{"slug":556,"name":556,"fn":557,"description":558,"org":559,"tags":560,"stars":26,"repoUrl":27,"updatedAt":566},"debug-reported-bug","reproduce and debug reported bugs","Reproduce-first bug diagnosis workflow. Use when a reported bug needs to be reproduced, reduced to a deterministic failing check, and traced through git history or `git bisect` so the exact cause is understood before any fix is attempted.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[561,562,565],{"name":24,"slug":25,"type":16},{"name":563,"slug":564,"type":16},"Git","git",{"name":428,"slug":429,"type":16},"2026-07-16T06:03:07.255013",{"slug":568,"name":568,"fn":569,"description":570,"org":571,"tags":572,"stars":26,"repoUrl":27,"updatedAt":577},"dependabot-triage","triage GitHub Dependabot alerts","Review current open Dependabot alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start dependency-update execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[573,574,575,576],{"name":52,"slug":41,"type":16},{"name":409,"slug":410,"type":16},{"name":484,"slug":485,"type":16},{"name":18,"slug":19,"type":16},"2026-07-29T05:39:38.757423",{"slug":579,"name":579,"fn":580,"description":581,"org":582,"tags":583,"stars":26,"repoUrl":27,"updatedAt":590},"environment-setup","configure local development environments","Internal skill to configure environments. Never use unless the user explicitly initiates the skill. Focus on localhost-ready setup and validation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[584,587],{"name":585,"slug":586,"type":16},"Configuration","configuration",{"name":588,"slug":589,"type":16},"Local Development","local-development","2026-08-01T05:44:46.333988",{"slug":592,"name":592,"fn":593,"description":594,"org":595,"tags":596,"stars":26,"repoUrl":27,"updatedAt":601},"explain-repo-code","explain repository code and architecture","Explanation-only repository workflow. Use when the user asks to understand behavior, architecture, or rationale from source context without modifying files.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[597,598],{"name":464,"slug":465,"type":16},{"name":599,"slug":600,"type":16},"Documentation","documentation","2026-07-16T06:00:34.090082"]