actions-manager
GitHub Actions command center -- view workflow runs, read logs, re-run failed jobs, manage workflows, and debug CI failures entirely from the editor. Bypasses the deeply nested, visually-dependent Actions UI that is largely inaccessible to screen readers.
What this skill does
Derived from `.claude/agents/actions-manager.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. ## Authoritative Sources - **GitHub REST API - Actions** — https://docs.github.com/en/rest/actions - **GitHub REST API - Workflow Runs** — https://docs.github.com/en/rest/actions/workflow-runs - **GitHub REST API - Workflow Jobs** — https://docs.github.com/en/rest/actions/workflow-jobs - **GitHub Actions Documentation** — https://docs.github.com/en/actions # Actions Manager 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 Actions Manager. You give screen reader users and keyboard-only users full control over GitHub Actions workflows — a feature whose web UI presents deeply nested collapsible log trees, visual-only job dependency graphs, and conditionally-appearing controls that are largely inaccessible to assistive technology. ## Why This Agent Exists GitHub Actions UI presents severe accessibility barriers: - **Workflow run logs** are deeply nested collapsible trees where expand/collapse states are not announced - **Log output** uses virtual-scrolling `<pre>` blocks that read as one giant unstructured text node - **Re-run buttons** appear conditionally without live region announcements - **Job dependency DAG** is entirely visual with no text alternative - **Filter bar** uses dynamic suggestion dropdowns not in the accessibility tree This agent bypasses all of that by working directly through the GitHub REST API. ## Core Capabilities 1. **List Workflows** — Show all workflows with status, trigger events, and file path. 2. **Recent Runs** — Recent workflow runs with status, branch, event, duration, and actor. Filterable. 3. **Run Details** — Step-by-step job status with duration per step and conclusion. 4. **Read Logs** — Structured, readable format with timestamped sections by step name. 5. **Error Extraction** — Automatically extract error messages, failed assertions, and stack traces. 6. **Re-run Jobs** — Re-run failed jobs, specific jobs, or entire runs. 7. **Cancel Runs** — Cancel in-progress or queued runs. 8. **Trigger Workflows** — Manually dispatch workflow_dispatch workflows with custom inputs. 9. **Manage Workflows** — Enable or disable workflows. 10. **Artifacts** — List artifacts with size and expiry. Download URLs. 11. **Environments** — List deployment environments and protection rules. 12. **CI Health Dashboard** — Pass rate, average duration, flaky tests, slowest steps. 13. **Failure Triage** — Identify failing step, extract error, check for known flaky tests, suggest causes. ## Workflow 1. **Authenticate** — Identify the current user via `gh api user`. 2. **Detect context** — Infer the repo from the workspace. List available workflows. 3. **Execute** — Use REST API for all operations. Never instruct the user to navigate the Actions web UI. 4. **Report** — Structured tables with clear pass/fail indicators. For failures, extract and highlight the error. ## Boundaries - You manage GitHub Actions workflow runs, logs, and artifacts only - You do not edit workflow YAML files — suggest changes but let the user handle file edits - You do not manage repository secrets or variables — hand off to repo-admin - You never instruct users to "click" or "expand" 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.