Discover blockchain divination mysticism skills, compare source repositories and read the instructions for each workflow.
Autonomous two-phase codebase exploration - first discovers natural perspectives (layers, components, boundaries), then dispatches adaptive deep-dive explorers based on what was discovered. Synthesizes findings...
Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only.
Patterns and structure for writing API reference documentation including endpoint descriptions, request/response schemas, and error documentation.
Analyzes codebase against standards and generates refactoring tasks for ring:dev-cycle.
Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology.
Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.
Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding.
Development cycle validation gate (Gate 5) - validates all acceptance criteria are met and requires explicit user approval before completion.
Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnostic patterns before concrete implementation choices.
Gate 0 of the development cycle. Executes code implementation using the appropriate specialized agent based on task content and project language. Handles TDD workflow with RED-GREEN phases. Follows project stan...
Patterns and structure for writing functional documentation including guides, conceptual explanations, tutorials, and best practices documentation.
Gate 2 of the development cycle. VALIDATES that observability was correctly implemented by developers. Does not implement observability code - only validates it.
Main orchestrator for the 6-gate development cycle system. Loads tasks/subtasks from PM team output and executes through implementation, devops, SRE, testing, review, and validation gates with state persistence...
Gate 7: Implementation tasks - value-driven decomposition into working increments that deliver measurable user value.
Technical writing specialists for functional and API documentation. Dispatch when you need to create guides, conceptual docs, or API references following established documentation standards.
Gate 2 sub-skill - validates uncertain mappings from Gate 1 and confirms all field specifications through testing.
All skills from obra/superpowers (skills/).
Use when Daem0nMCP tools are available - enforces the sacred covenant (commune at session start, seek counsel before changes, inscribe decisions, seal outcomes)
Quick guide to choosing the right creative writing skill. Use when you need help deciding which creative writing skill to use for a specific task - brainstorming vs documentation, critique vs writing, etc.
A test skill that responds to the magic word "flarglebargle" with a compliment. Use for testing skill activation and trigger functionality.
Advanced document search with BM25 keyword matching, semantic vector search, and hybrid retrieval. Enables precise technical queries, conceptual understanding, and intelligent result fusion. Supports local docu...
Guidance for generating legal chess moves using only regex pattern matching and substitution. This skill applies when implementing chess move generators constrained to regex-only solutions, FEN notation parsing...
Guidance for implementing differential cryptanalysis attacks on FEAL and similar Feistel ciphers. This skill should be used when asked to break FEAL encryption, recover cipher keys through differential attacks,...
Guide for performing linear cryptanalysis attacks on FEAL and similar Feistel ciphers. This skill should be used when tasks involve breaking FEAL encryption, recovering cipher keys using known plaintext-ciphert...
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.