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

tdd-full-coverage

troykelly

Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement

GitHub

review-gate

troykelly

HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met

GitHub

inclusive-language

troykelly

Use when writing code, documentation, or comments - always use accessible and respectful terminology

GitHub

github-api-cache

troykelly

MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.

GitHub

skill-development

troykelly

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, prog...

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

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

issue-driven-development

troykelly

Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification

GitHub

work-intake

troykelly

Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.

GitHub

no-deferred-work

troykelly

Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission

GitHub

sentry-setup-ai-monitoring

troykelly

Setup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically dete...

GitHub

issue-lifecycle

troykelly

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

GitHub

clean-commits

troykelly

Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point

GitHub

timescaledb

troykelly

MANDATORY when working with time-series data, hypertables, continuous aggregates, or compression - enforces TimescaleDB 2.24.0 best practices including lightning-fast recompression, UUIDv7 continuous aggregates...

GitHub

documentation-audit

troykelly

Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.

GitHub

silent-failure-hunter

troykelly

Use when asked to detect silent failures/weak error handling or explicitly asked to run the silent-failure-hunter subagent.

GitHub

issue-driven-development

troykelly

Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification

GitHub

sentry-setup-tracing

troykelly

Setup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScr...

GitHub

tdd-full-coverage

troykelly

Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement

GitHub

feedback-triage

troykelly

Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type an...

GitHub

initiative-architecture

troykelly

Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones...

GitHub

postgres-rls

troykelly

MANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Level Security best practices and catches common bypass vulnerabilities

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.