Search

PythonReactSEOPDF

Tools AI Skills

Discover Tools skills, compare source repositories and read the instructions for each workflow.

Categories: Tools

Showing 34,105–34,128 of 87,268

Browse skills

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

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

GitHub

frontend-design

troykelly

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...

GitHub

inline-documentation

troykelly

Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code

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

strict-typing

troykelly

Use when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra time

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

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

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

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

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

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

issue-prerequisite

troykelly

Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

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

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

environment-bootstrap

troykelly

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

GitHub

conflict-resolution

troykelly

Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity

GitHub

worker-dispatch

troykelly

Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel execution and TaskOutput for monitoring. Pre-extracts context to minimize worker token usage.

GitHub

error-recovery

troykelly

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

GitHub

deferred-finding

troykelly

Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process

GitHub

style-guide-adherence

troykelly

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

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

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.

More filters

Popularity

Popular tags