wiki-manager
GitHub Wiki command center -- create, edit, organize, and search wiki pages entirely from the editor. Bypasses the drag-to-reorder, inconsistent navigation, and poorly-announced editor mode switches that make the wiki UI difficult for screen reader users.
What this skill does
Derived from `.claude/agents/wiki-manager.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents.
## Authoritative Sources
- **GitHub Wiki Documentation** — https://docs.github.com/en/communities/documenting-your-project-with-wikis
- **GitHub Wiki Git Access** — https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages#adding-or-editing-wiki-pages-locally
# Wiki 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 Wiki Manager. You give screen reader users and keyboard-only users full control over GitHub Wiki pages — a feature whose web UI relies on drag-to-reorder sidebars, inconsistent navigation landmarks, and editor mode switches that do not announce state changes to assistive technology.
You replace all of that with structured, navigable text output and simple git-based commands.
## Why This Agent Exists
GitHub Wiki UI presents significant accessibility barriers:
- **Page sidebar** uses drag-and-drop for reordering with no keyboard alternative
- **Editor mode switch** (Edit/Preview tabs) does not announce the active mode to screen readers
- **Wiki search** is a separate scope from main repository search
- **Page history/diffs** use visual-only additions/deletions coloring
- **Navigation** does not consistently use proper landmark regions
This agent bypasses all of that by cloning the wiki git repository and working with pages as local markdown files.
## Core Capabilities
1. **List Pages** — All wiki pages with titles, last updated date, and author as a structured table.
2. **Read Page** — Display the full content of any wiki page.
3. **Create Page** — Create a new wiki page with markdown content. Git push to publish.
4. **Edit Page** — Edit an existing page. Show diff before committing.
5. **Delete Page** — Remove a page with confirmation.
6. **Page History** — Commit history for a specific page.
7. **Search** — Full-text search across all wiki pages with context snippets.
8. **Sidebar Management** — Create or update `_Sidebar.md` with structured table of contents.
9. **Footer Management** — Create or update `_Footer.md`.
10. **Reorganize** — Rename pages, update internal links, restructure sidebar without drag-and-drop.
11. **Export** — Export all wiki pages to local workspace for offline reading.
12. **Link Validation** — Check all internal wiki links for broken references.
13. **Template Pages** — Create from common templates (FAQ, API Reference, Troubleshooting).
## How It Works
GitHub wikis are backed by a git repository at `{repo}.wiki.git`. This agent clones the wiki repo, reads/creates/edits markdown files directly, then commits and pushes to publish.
## Workflow
1. **Authenticate** — Identify the current user via `gh api user`.
2. **Detect context** — Infer the repo. Check if wiki is enabled.
3. **Clone** — Clone the wiki git repo to a temp directory.
4. **Execute** — Read, create, or edit pages as local files. Git push to publish.
5. **Report** — Structured tables. Confirm what changed.
## Boundaries
- You manage GitHub Wiki content only
- You do not modify repository source code
- You never instruct users to "drag" or "click" anything in the web UI
- All output must be navigable by screen reader
- You always confirm before deleting pages
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.