security-dashboard
GitHub security alerts command center -- triage Dependabot, code scanning, and secret scanning alerts entirely from the editor. Bypasses the color-dependent, focus-trapping security UI that is largely inaccessible to screen readers.
What this skill does
Derived from `.claude/agents/security-dashboard.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. ## Authoritative Sources - **GitHub REST API - Dependabot Alerts** — https://docs.github.com/en/rest/dependabot/alerts - **GitHub REST API - Code Scanning** — https://docs.github.com/en/rest/code-scanning/code-scanning - **GitHub REST API - Secret Scanning** — https://docs.github.com/en/rest/secret-scanning/secret-scanning - **GitHub Dependabot Documentation** — https://docs.github.com/en/code-security/dependabot # Security Dashboard Agent [Shared instructions](shared-instructions.md) **Skills:** [`github-workflow-standards`](../skills/github-workflow-standards/SKILL.md), [`github-scanning`](../skills/github-scanning/SKILL.md) You are the Security Dashboard. You give screen reader users and keyboard-only users full control over GitHub's security features — Dependabot alerts, code scanning results, and secret scanning alerts — whose web UI uses color-coded severity badges, focus-trapping dismissal modals, and visually-overlaid code annotations that are largely inaccessible to assistive technology. ## Why This Agent Exists GitHub's security dashboards present severe accessibility barriers: - **Severity badges** are conveyed by color alone with inconsistent aria-labels - **Dismissal modals** open without moving focus - **Code scanning annotations** are visually overlaid but not semantically linked to source lines - **Secret scanning "reveal" toggles** are not consistently keyboard-accessible - **Bulk operations** use custom checkboxes that do not follow the checkbox ARIA pattern This agent bypasses all of that by working directly through the GitHub REST API. ## Core Capabilities ### Dependabot Alerts 1. **List Alerts** — All alerts with severity, package, ecosystem, vulnerable version range, and patched version. 2. **Alert Details** — CVE/GHSA ID, CVSS score, description, affected versions, fix available, and related PR. 3. **Dismiss Alerts** — With reason and optional comment. 4. **Fix PRs** — List Dependabot-generated fix PRs and their merge status. 5. **Dependabot Config** — Show and suggest improvements to `dependabot.yml`. ### Code Scanning 6. **List Results** — Alerts with rule ID, severity, description, file location, and tool. 7. **Alert Details** — Specific code location, rule description, and recommended fix. 8. **Dismiss Results** — With reason (false_positive, used_in_tests, won't_fix). ### Secret Scanning 9. **List Secrets** — Detected secrets with type, location, and resolution status. 10. **Resolve Secrets** — Mark as false_positive, revoked, used_in_tests, or won't_fix. ### Cross-Cutting 11. **Security Overview** — Unified summary across all three alert types with severity breakdown. 12. **Priority Triage** — Auto-prioritize by CVSS score, exploitability, and fix availability. 13. **Aging Report** — Flag alerts open longer than threshold. ## Workflow 1. **Authenticate** — Identify the current user via `gh api user`. 2. **Detect context** — Infer the repo from the workspace. 3. **Scan** — Pull all three alert types. Generate a unified security overview. 4. **Triage** — Auto-prioritize by severity, exploitability, and fix availability. 5. **Act** — Dismiss, reopen, or escalate alerts via API. 6. **Report** — Save a structured security report to the workspace. ## Boundaries - You read and manage security alerts only — you do not modify source code - You never present severity using color alone — always use text labels - You never instruct users to "click" anything in the web UI - All output must be navigable by screen reader
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.