All authors
Claude Skills by oborchers
github.com/oborchers109 skills0 installs15 views
- Architecture ReviewRun Proqi's deliberate repository-wide architecture audit with independent Codex and Claude Fable reviews, synthesize evidence, and complete a behavior-preserving refactor on main. Use for a global architecture pass, not an ordinary feature or pull-request review.Votes: 0GitHub stars: 43
- Claude Code ReviewRun a general read-only implementation review with Claude Code as a native background subagent from Claude Code, or through the non-interactive Claude Code CLI from another harness. Never create a Herdr pane, tab, workspace, or agent for a reviewer. Do not use for Proqi's repository-wide architecture review.Votes: 0GitHub stars: 43
- Codex ReviewRun a bounded read-only implementation review with Codex as a native background subagent from Codex, or through the non-interactive Codex CLI from another harness. Never create a Herdr pane, tab, workspace, or agent for a reviewer.Votes: 0GitHub stars: 43
- Implement In WorktreeOrchestrate one implementation ticket in one isolated Git worktree with one Herdr-managed coding agent, one goal, verification, and a pull request. Use only when explicitly invoked from inside Herdr.Votes: 0GitHub stars: 43
- Proqi ScreenshotCapture or regenerate public Proqi README screenshots of real Codex and Codex-plus-Proqi Herdr panes with controlled geometry, synthetic content, privacy review, and exact asset validation.Votes: 0GitHub stars: 43
- ReleasePrepare, verify, publish, or diagnose a Proqi release through the repository's protected tag workflow. Use only when explicitly invoked for this repository.Votes: 0GitHub stars: 43
- WalkthroughDeliver an evidence-grounded, one-item-at-a-time walkthrough of a Proqi implementation worktree or one dedicated GitHub pull request, including a live Herdr TUI demonstration when behavior is visual. Use when explicitly invoked with $walkthrough or when the user directly asks to be walked through Proqi work. Continue the active walkthrough when the user replies next.Votes: 0GitHub stars: 43
- Proqi DebugDiagnose a reported Proqi failure using its content-redacted local diagnostics, stable CLI errors, and documented SQLite model. Use only when the user explicitly asks to debug Proqi or prepare a Proqi issue.Votes: 0GitHub stars: 43
- ProqiInspect or update one user-specified Proqi scratchpad session through the installed version's JSON CLI. Use only when the user explicitly invokes Proqi or names this skill.Votes: 0GitHub stars: 43
- Agent BatonThis skill should be used when work must be chained across two independent agent processes that share no parent session — e.g. one agent in one terminal finishes a task and a second agent (possibly a different tool entirely: Claude Code, Codex, Cursor, Gemini) must start only once the first is done. Covers passing a baton (publishing a completion signal), attaching an optional free-form payload for the next agent to read as context, waiting for a baton (blocking until it appears, with a deadl...Votes: 0GitHub stars: 34
- Advanced PatternsThis skill should be used when the user is implementing bulk or batch API operations, choosing between REST and GraphQL or gRPC, designing real-time APIs with SSE or WebSockets, implementing multi-tenant API isolation, setting up API gateways, or applying CQRS and event sourcing patterns. Covers batch operations, protocol comparison, real-time patterns, multi-tenancy, and API gateway selection.Votes: 0GitHub stars: 34
- Auth And Api KeysThis skill should be used when the user is designing API authentication, implementing API keys with prefixes, choosing between API keys and OAuth, setting up JWT tokens, implementing Bearer token authentication, designing API key rotation, or scoping API key permissions. Covers Stripe-style prefixed keys (sk_live_, pk_test_), OAuth 2.0 flows, JWT patterns, and key management.Votes: 0GitHub stars: 34
- Caching And PerformanceThis skill should be used when the user is implementing HTTP caching, configuring Cache-Control headers, using ETags and conditional requests, setting up CDN caching for APIs, implementing response compression, choosing between gzip and Brotli, configuring HTTP/2, or implementing circuit breakers. Covers Cache-Control directives, ETag validation, CDN strategies, compression, and resilience patterns.Votes: 0GitHub stars: 34
- Documentation And DxThis skill should be used when the user is writing API documentation, designing developer onboarding, building interactive API explorers, generating SDKs, creating code examples, setting up sandbox environments, implementing API changelogs, or optimizing time-to-first-API-call. Covers three-panel docs layout, interactive try-it functionality, multi-language examples, and developer experience optimization.Votes: 0GitHub stars: 34
- Errors And Status CodesThis skill should be used when the user is designing API error responses, choosing HTTP status codes, implementing error envelopes, handling validation errors, creating per-field error messages, or following RFC 9457 Problem Details. Covers status code selection (2xx-5xx), consistent error formats, Stripe/GitHub/Twilio error patterns, and request/trace ID correlation.Votes: 0GitHub stars: 34
- Http MethodsThis skill should be used when the user is choosing HTTP methods for API endpoints, designing CRUD operations, implementing idempotent operations, deciding between PUT and PATCH, handling bulk operations, or working with HTTP verb semantics. Covers GET, POST, PUT, PATCH, DELETE with idempotency rules, status code pairings, and real-world patterns.Votes: 0GitHub stars: 34
- Prefixed IdsThis skill should be used when the user is designing ID formats for API resources, implementing type-safe identifiers, choosing between UUID and prefixed IDs, generating IDs with KSUID or ULID, creating ID validation, or following Stripe's prefixed ID pattern. Covers prefix conventions, ID generation, validation, and debugging benefits.Votes: 0GitHub stars: 34
- Rate Limiting And SecurityThis skill should be used when the user is implementing rate limiting, choosing rate limit algorithms, adding rate limit headers, securing API endpoints, preventing OWASP API Top 10 vulnerabilities, configuring CORS, validating input, or implementing request signing. Covers sliding window, token bucket, and leaky bucket algorithms, rate limit response headers, and API security best practices.Votes: 0GitHub stars: 34
- Response Design And PaginationThis skill should be used when the user is designing API response formats, implementing pagination (cursor, offset, keyset), creating list endpoints, designing response envelopes, implementing expandable/embeddable objects, or structuring API output. Covers Stripe-style cursor pagination, consistent list envelopes, expand patterns, and response metadata.Votes: 0GitHub stars: 34
- Routes And NamingThis skill should be used when the user is designing API routes, URL structures, endpoint naming, resource naming conventions, query parameters vs path parameters, JSON field naming (snake_case vs camelCase), nesting depth, or API URL patterns. Covers plural nouns, flat vs hierarchical URLs, field naming conventions, and real-world patterns from Stripe, GitHub, Twilio, and Google.Votes: 0GitHub stars: 34
- Using Api PrinciplesThis skill should be used when the user asks "which API design skill should I use", "show me all API principles", "help me pick an API pattern", or at the start of any RESTful API design conversation. Provides the index of all twelve principle skills and ensures the right ones are invoked before any API design work begins.Votes: 0GitHub stars: 34
- Versioning And EvolutionThis skill should be used when the user is designing API versioning strategy, choosing between URL path and header-based versioning, implementing Stripe-style date-based versioning, planning API deprecation, using sunset headers, or evolving an API without breaking clients. Covers URL versioning, additive evolution, backward compatibility, and deprecation communication.Votes: 0GitHub stars: 34
- Webhooks And EventsThis skill should be used when the user is designing webhook systems, implementing webhook signing with HMAC-SHA256, building webhook retry logic, choosing event naming conventions, handling webhook ordering, implementing webhook endpoints, or building event-driven API integrations. Covers Stripe-style webhook patterns, signature verification, exponential backoff retries, and event deduplication.Votes: 0GitHub stars: 34
- Architecture Decision RecordsThis skill should be used when the user is making significant infrastructure decisions, documenting architectural choices, creating decision records, tracking exemptions from IaC, establishing decision-making processes, or onboarding new team members to existing infrastructure. Covers ADR format, numbering, status lifecycle, exemption tracking, and decision governance.Votes: 0GitHub stars: 34
- Container Image TaggingThis skill should be used when the user is building Docker images, configuring container registries, designing image tagging strategies, setting up registry lifecycle policies, debugging production incidents that require tracing running code, or discussing OCI labels and build metadata. Covers git SHA tagging, the traceability chain from container to source code, registry retention policies, OCI build labels, and why date-based or environment-based tags fail.Votes: 0GitHub stars: 34
- Managed Services Over Self HostedThis skill should be used when the user is choosing between managed and self-hosted services, deciding whether to run Kubernetes or use managed containers, evaluating self-hosted databases vs managed databases, considering self-hosted monitoring or caches, designing for a small team (under 50 engineers), or justifying a self-hosted exception. Covers the operations tax of self-hosting, managed container orchestration over Kubernetes for small teams, managed workflow engines, managed caches and...Votes: 0GitHub stars: 34
- Multi Account From Day OneThis skill should be used when the user is setting up a new cloud project, designing account or project structure, creating environment isolation, configuring organization units or management groups, implementing landing zones, or deciding how to separate dev and prod workloads. Covers multi-account strategy, blast radius isolation, landing zone setup, and organizational governance.Votes: 0GitHub stars: 34
- Naming And Labeling As CodeThis skill should be used when the user is designing resource naming conventions, implementing tagging or labeling strategies, building a labels module, setting up cost center attribution, creating naming standards for cloud resources, or reviewing tag compliance. Covers naming patterns, labels modules, cost center validation, tag enforcement, and naming across resource types.Votes: 0GitHub stars: 34
- Network ArchitectureThis skill should be used when the user is designing VPC or virtual network topology, planning subnet tiers, configuring NAT gateways, setting up DNS zones, creating private connectivity endpoints, designing API gateway routing, or planning CIDR ranges. Covers subnet tiers (baseline and optional), availability zone distribution, cost-optimized NAT, private service endpoints, DNS strategy, and API gateway patterns.Votes: 0GitHub stars: 34
- Operational HygieneThis skill should be used when the user is addressing cloud resource sprawl, implementing cost attribution and tagging enforcement, setting up monitoring and alerting defaults, configuring drift detection for Terraform, designing lifecycle policies for storage and artifacts, or cleaning up after migrations. Covers resource cleanup discipline, cost center enforcement, monitoring with sensible defaults, scheduled drift detection, and lifecycle automation.Votes: 0GitHub stars: 34
- Repository And State StrategyThis skill should be used when the user is structuring Terraform repositories, deciding between mono-repo and multi-repo strategies, organizing infrastructure into layers, designing state management architecture, setting up cross-layer dependencies, or evaluating blast radius of infrastructure changes. Covers multi-repository strategy, numbered layer architecture, state-per-layer-per-environment isolation, cross-layer remote state references, and deployment ordering.Votes: 0GitHub stars: 34
- Secrets And Configuration ManagementThis skill should be used when the user is storing credentials, managing API keys, setting up secret rotation, designing secret naming conventions, creating database users, managing environment-specific configuration, or deciding how applications should access secrets at runtime. Covers the one-secret-per-service pattern, account-based environment isolation, KMS encryption, role-based database users, and the infrastructure wiring exception for parameter stores.Votes: 0GitHub stars: 34
- Security Monitoring From Day OneThis skill should be used when the user is setting up security monitoring, enabling threat detection, configuring compliance scanning, deploying vulnerability scanners, creating a security account, centralizing security findings, choosing between detective and preventive controls, or deciding when to enable security services. Covers the four security pillars (threat detection, compliance scanning, vulnerability scanning, configuration auditing), centralized security accounts with delegated ad...Votes: 0GitHub stars: 34
- Service Owned InfrastructureThis skill should be used when the user is deciding where infrastructure code should live, structuring service repositories with Terraform, separating shared vs service-owned resources, designing module consumption patterns, or eliminating centralized deployment bottlenecks. Covers service-owned IaC directories, remote state consumption, shared module guardrails, and the boundary between platform and service infrastructure.Votes: 0GitHub stars: 34
- Tag Based Production DeploysThis skill should be used when the user is designing CI/CD pipelines, configuring deployment triggers, setting up production release processes, implementing approval gates, configuring pre-commit hooks for Terraform, or distinguishing between development and production deployment strategies. Covers the environment/trigger matrix, git tag naming conventions, manual approval gates, pre-commit validation, the full pipeline flow from commit to production, and why branch-based production deploys a...Votes: 0GitHub stars: 34
- Terraform Module PatternsThis skill should be used when the user is designing Terraform modules, wrapping community modules, implementing conditional resource creation, structuring module variables and outputs, setting up pre-commit quality gates, versioning custom modules, building reusable infrastructure components, or reviewing module code for maintainability. Covers ten production-proven module design patterns, quality gate configuration, and version pinning strategies.Votes: 0GitHub stars: 34
- Unified Cicd PlatformThis skill should be used when the user is choosing a CI/CD platform, migrating between CI/CD providers, consolidating build and deployment pipelines, designing pipeline architecture across application and infrastructure code, setting up drift detection, configuring OIDC authentication for pipelines, or discussing the operational cost of multiple CI/CD systems. Covers platform selection, the cost of multi-platform CI/CD, what 'everything on one platform' means, OIDC pipeline authentication, J...Votes: 0GitHub stars: 34
- Using Cloud Foundation PrinciplesThis skill should be used when the user asks "which cloud foundation skill should I use", "show me all cloud principles", "help me pick an infrastructure pattern", or at the start of any cloud infrastructure, Terraform, or IaC conversation. Provides the index of all fifteen principle skills and ensures the right ones are invoked before any cloud infrastructure work begins.Votes: 0GitHub stars: 34
- Zero Static CredentialsThis skill should be used when the user is configuring SSO, setting up CI/CD authentication, designing OIDC federation, eliminating SSH keys or VPN, managing human or machine identity, or discussing credential lifecycle. Covers core access patterns (human SSO, pipeline OIDC, operator session-based), federated identity, workload identity federation, and the elimination of static API keys, SSH keys, and VPN files.Votes: 0GitHub stars: 34
- Hallucination PreventionThis skill should be used when producing any research output, verifying claims from web sources, checking citation accuracy, assessing confidence in findings, preventing hallucination cascading across agent boundaries, or reviewing research documents for factual reliability. Covers the hallucination taxonomy (7 types), OWASP ASI08 cascading failures, circuit breaker patterns, citation verification rules, confidence scoring, ground-truth validation, and known limitations of automated verificat...Votes: 0GitHub stars: 34
- Research MethodologyThis skill should be used when starting any research task, decomposing a research query, planning research strategy, deciding how many sub-topics to investigate, scaling research effort to query complexity, determining when to stop researching, or dynamically re-planning based on intermediate findings. Covers query analysis, decomposition techniques (Self-Ask, Least-to-Most, DAG-based), effort scaling, plan representations, stopping criteria, and research anti-patterns.Votes: 0GitHub stars: 34
- Source EvaluationThis skill should be used when evaluating source credibility, deciding which search results to trust, choosing between search providers, detecting SEO spam or content farms, selecting domain-specific sources (academic, medical, legal, technical), evaluating software packages or libraries, comparing tools or technologies, assessing GitHub repo health, checking adoption metrics, or when research quality depends on retrieval quality. Covers the source credibility taxonomy (T1-T6 tiers), CRAAP fr...Votes: 0GitHub stars: 34
- Synthesis And ReportingThis skill should be used when combining research findings from multiple sources or agents, deduplicating overlapping information, resolving conflicts between sources, constructing a narrative from research data, formatting citations and source lists, assessing report quality, or writing the final research document. Covers deduplication strategies, conflict resolution, thematic analysis, narrative construction, citation management, and synthesis anti-patterns.Votes: 0GitHub stars: 34
- Using Deep ResearchThis skill should be used when the user asks 'how do I do deep research', 'show me research skills', 'help me research a topic', 'what research methodology should I use', or at the start of any structured web research task. Provides the index of all deep research principle skills and the /research command.Votes: 0GitHub stars: 34
- Markdown CompressionThis skill should be used when the user asks to 'compress markdown', 'shrink this file', 'optimize tokens', 'reduce file size', 'compress instructions', 'make this more concise', 'minimize this prompt', 'compress CLAUDE.md', 'compress ARCHITECTURE.md', 'optimize agent instructions', or wants to reduce token usage in LLM-facing markdown files. Covers lossless structural optimization and lossy semantic compression with section-by-section analysis.Votes: 0GitHub stars: 34
- Abbreviation PolicyThis skill should be used when the user is abbreviating identifiers, using acronyms, or when a codebase has inconsistent short forms like btn/button, msg/message, req/request. Covers the abbreviation decision framework, approved short forms, and the rule that consistency beats brevity.Votes: 0GitHub stars: 34
- Boolean NamingThis skill should be used when the user is naming boolean variables, writing predicate functions, using flags or toggles, or when code contains ambiguous boolean names like flag, status, check, active without proper prefixes. Covers is/has/can/should prefixes, positive naming, and the rule that a boolean's name must read as a true/false question.Votes: 0GitHub stars: 34
- Casing LawThis skill should be used when the user is writing code with mixed casing conventions, choosing casing for identifiers, enforcing casing consistency across a codebase, or when camelCase and snake_case appear in the same file. Covers per-context casing rules, acronym handling, and the absolute prohibition of mixed conventions.Votes: 0GitHub stars: 34
- Dead Code IntoleranceThis skill should be used when the user's code contains commented-out code blocks, unused imports, unreachable branches, TODO/FIXME comments that have been sitting for more than a day, or comments referencing removed functionality. Covers the elimination of dead code and the rule that version control remembers so you don't have to.Votes: 0GitHub stars: 34
- Declaration OrderThis skill should be used when the user is organizing code within a file, ordering class members, structuring module exports, or when a file has constants mixed with functions mixed with classes in no predictable order. Covers file-level ordering, class member ordering, and the rule that every file should have the same shape.Votes: 0GitHub stars: 34