Search

PythonReactSEOPDF

Veraticus AI Skills

GitHub ↗

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

Author statistics

Indexed skills

13

Repository stars across indexed skills

0

Repository forks

0

Average repository stars per indexed skill

0

Repository stars may repeat across skills from the same repository.

13 skills

Browse skills

GitHub

using-gambit

Veraticus

Use at session start - establishes mandatory workflows for finding and using skills

GitHub

executing-plans

Veraticus

Executes Tasks one at a time with mandatory human checkpoints. Reviews learnings, then STOPS for user review before continuing.

GitHub

task-refinement

Veraticus

Use when refining Tasks into actionable plans - SRE-style review ensuring corner cases handled, junior engineer can execute without questions

GitHub

finishing-branch

Veraticus

Use when implementation complete and tests pass - verifies all tasks done, presents integration options (merge/PR/keep/discard), executes choice

GitHub

refactoring

Veraticus

Use when improving code structure without changing behavior - test-preserving transformations in small steps, running tests between each change

GitHub

testing-quality

Veraticus

Use to audit test quality with SRE-level scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases

GitHub

code-review

Veraticus

Use for requesting and receiving code reviews - dispatch reviewer agent for self-review, verify feedback before implementing, no performative agreement

GitHub

using-worktrees

Veraticus

Use when starting feature work that needs isolation - creates git worktrees with smart directory selection, safety verification, and environment setup

GitHub

brainstorming

Veraticus

Refines rough ideas into epic Tasks with immutable requirements through Socratic questioning. Use before any creative work.

GitHub

parallel-agents

Veraticus

Use when facing 3+ independent failures that can be investigated without shared state - dispatches multiple agents concurrently to investigate and fix problems in parallel

GitHub

test-driven-development

Veraticus

Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code

GitHub

verification

Veraticus

Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always

GitHub

debugging

Veraticus

Use when encountering bugs, test failures, or unexpected behavior - systematic root cause analysis before fixes, tools first, regression test required

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.