Search

PythonReactSEOPDF

troykelly AI Skills

GitHub ↗

Browse published AI skills maintained by troykelly. Compare skill descriptions and follow each source repository for setup instructions.

Author statistics

Indexed skills

128

Repository stars across indexed skills

640

Repository forks

61

Average repository stars per indexed skill

5

Repository stars may repeat across skills from the same repository.

128 skills

Browse skills

GitHub

comprehensive-review

troykelly

Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete

GitHub

sentry-setup-metrics

troykelly

Setup Sentry Metrics in any project. Use this when asked to add Sentry metrics, track custom metrics, setup counters/gauges/distributions, or instrument application performance metrics. Supports JavaScript, Typ...

GitHub

research-after-failure

troykelly

Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming

GitHub

features-documentation

troykelly

Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.

GitHub

apply-all-findings

troykelly

Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace

GitHub

security-review

troykelly

MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code

GitHub

environment-bootstrap

troykelly

Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions

GitHub

security-reviewer

troykelly

Use when explicitly asked to run the security-reviewer subagent or when another skill requires the security-reviewer agent card.

GitHub

worker-protocol

troykelly

Defines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.

GitHub

pre-work-research

troykelly

Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach

GitHub

code-architect

troykelly

Use when asked for an architecture blueprint or explicitly asked to run the code-architect subagent.

GitHub

ipv6-first

troykelly

IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.

GitHub

code-simplifier

troykelly

Use when asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.

GitHub

error-recovery

troykelly

Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state

GitHub

postgis

troykelly

MANDATORY when working with geographic data, spatial queries, geometry operations, or location-based features - enforces PostGIS 3.6.1 best practices including ST_CoverageClean, SFCGAL 3D functions, and bigint...

GitHub

sentry-setup-logging

troykelly

Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby...

GitHub

agent-development

troykelly

Use when the user wants to design Codex agent equivalents (specialized workers/profiles/prompt files), define triggering conditions, or build reusable agent prompts and validation tools.

GitHub

style-guide-adherence

troykelly

Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language

GitHub

local-service-testing

troykelly

Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks

GitHub

worker-dispatch

troykelly

Use to spawn isolated worker processes for autonomous issue work. Creates git worktrees, constructs worker prompts, and handles worker lifecycle.

GitHub

api-documentation

troykelly

Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.

GitHub

issue-lifecycle

troykelly

Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end

GitHub

hook-development

troykelly

Use when the user wants to create Codex workflow hooks (pre/post run gates, tool-use validators, stop checks) or needs guidance on hook scripts and hooks.json configuration.

GitHub

project-status-sync

troykelly

Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields

The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.