Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
pai-monitor
Monitor Personal AI Infrastructure repo for updates and identify improvement opportunities for Geoffrey. Use when you want to sync Geoffrey with PAI's latest patterns, packs, or architectural decisions.
krishagel/geoffrey 4
-
elevenlabs-tts
Generate high-quality audio from text using Eleven Labs API. Use for podcasts, narration, voice-overs, and audio summaries.
krishagel/geoffrey 4
-
local-tts
Local text-to-speech using MLX and Kokoro model
krishagel/geoffrey 4
-
pptx
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
krishagel/geoffrey 4
-
redrover-manager
Access Red Rover absence management data for PSD staff attendance tracking and reporting
krishagel/geoffrey 4
-
psd-instructional-vision
Peninsula School District's instructional framework and pedagogical beliefs. Use when creating graphics about PSD instruction, designing AI assistants for educators, writing about good teaching practices, or sharing PSD's educational philosophy with external systems.
krishagel/geoffrey 4
-
seven-advisors
Seven Advisors decision council - structured multi-perspective deliberation for important decisions. Use when facing complex choices, strategic decisions, or when you need to think through a problem from multiple angles.
krishagel/geoffrey 4
-
morning-briefing
Generate comprehensive morning briefing with calendar, tasks, tickets, news, and weather. Saves to Obsidian, sends email with audio podcast attached.
krishagel/geoffrey 4
-
multi-model-research
Orchestrate multiple frontier LLMs (Claude, GPT-5.1, Gemini 3.0 Pro, Perplexity Sonar, Grok 4.1) for comprehensive research using LLM Council pattern with peer review and synthesis
krishagel/geoffrey 4
-
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update 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. Make sure to use this skill whenever the user mentions creating, building, designing, or improving skills, even if they don't explicitly say "skill-creator".
krishagel/geoffrey 4
-
psd-brand-guidelines
Apply Peninsula School District official brand colors, typography, and logos to artifacts
krishagel/geoffrey 4
-
ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
petekp/claude-code-setup 20
-
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
petekp/claude-code-setup 20
-
manage-codex
Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.
petekp/claude-code-setup 20
-
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
petekp/claude-code-setup 20
-
capture-learning
Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.
petekp/claude-code-setup 20
-
agent-changelog
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
petekp/claude-code-setup 20
-
swift-apps
Build, refactor, review, and debug native Apple-platform software in Swift. Use when working on `.swift` files, SwiftUI views, Observation-based state, `@Bindable` and binding flow, SwiftData-backed UI, scenes and windows, search/navigation structures, UIKit/AppKit interop, Liquid Glass adoption, macOS-native UX, or SwiftUI performance/accessibility. Trigger on requests to create or polish iOS, iPadOS, macOS, or visionOS features; clean up SwiftUI view structure; diagnose jank or invalidation storms; review app quality; or make a feature feel like a good Apple-platform citizen.
petekp/claude-code-setup 20
-
tdd
Test-driven development for features, bug fixes, regressions, and safe refactors using a failing-test-first workflow. Use when Codex needs to add or change behavior with proof, reproduce a bug in a test, write regression or characterization tests, make a refactor safer, or respond to prompts like "use TDD", "red-green-refactor", "write the test first", "add a regression test", "reproduce this in a test", "prove the fix", "cover this change with tests", or "make this safe to refactor". Prefer this skill when confidence should come from executable evidence instead of reasoning alone.
petekp/claude-code-setup 20
-
method:research-to-implementation
Artifact-driven method for taking a significant feature from idea to shipped code. 10 steps across 5 phases: Alignment → Evidence → Decision → Preflight → Delivery. Use when the user describes a non-trivial feature that needs research, design, and implementation — not for bug fixes, single-file changes, or quick wiring tasks.
petekp/claude-code-setup 20
-
literate-guide
Create a narrative guide to a codebase or feature in the style of Knuth's Literate Programming — code and prose interwoven as a single essay, ordered for human understanding rather than compiler needs. Use when the user asks to 'explain this codebase as a story', 'write a literate guide', 'create a narrative walkthrough', 'tell the story of this code', 'Knuth-style documentation', 'weave a guide for this feature', or when they want deep, readable documentation that treats the program as literature. Also trigger when someone wants a document that a thoughtful reader could follow from start to finish and come away understanding both WHAT the code does and WHY every design choice was made.
petekp/claude-code-setup 20
-
method:dry-run
Validate a Claude Code method skill for mechanical soundness by dry-running a concrete feature through every step. Use when you need to dry run, validate a method, trace a method skill, check mechanical soundness, or verify that a method's setup, paths, commands, artifact chains, headers, templates, gates, and topology are wired correctly. Invoke this after authoring or editing any method skill, and before trusting it for real work.
petekp/claude-code-setup 20
-
exhaustive-systems-analysis
Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.
petekp/claude-code-setup 20
-
method:decision-pressure-loop
Architecture decision workflow for choosing between meaningful architectural or protocol options under uncertainty before implementation begins. 8 steps across 5 phases: Framing -> Reality Mapping -> Option Exploration -> Pressure -> Publication. Use when the team needs a defensible decision with explicit tradeoffs, reopen conditions, and implementation-facing guidance — not when the goal is already code delivery.
petekp/claude-code-setup 20