Loading...
Loading...
Found 2,056 Skills
Document lessons, update rules/templates/docs. Use to capture learnings after review.
Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.
Roll up the monthly memory log from weekly entries.
Create outcome spec (overview, decisions, steps, edge cases). Use $ARGUMENTS as spec topic if provided.
Evaluate output, identify lessons, decide accept/rework. Use after implementation.
Generate a GROOVE.md onboarding guide for contributors to a groove-enabled project. Explains the compound loop, commands, and conventions.
Publish a workflow learning to the groovebook shared commons as a GitHub PR. Use after groove-work-compound when a learning is worth sharing.
Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.
Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.
Binance Fiat request using the Binance API. Authentication requires API key and secret key.
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.