This Skill enforces a high-signal workflow to avoid jumping straight into coding.

Extract 2–12 epics (depending on complexity) for an idea using concept_summary.md as the semantic anchor (writes to ideas/<IDEA_ID>/runs and updates ideas/<IDEA_ID>/latest)

epic-initializer

Epic and task structure patterns for SpecFlux. Use when breaking PRDs into epics and tasks. Epics should be self-contained with clear acceptance criteria.

Guide on testing with Vitest and Playwright for Epic Stack

Validate epics_backlog.md for an idea against concept_summary.md (writes report to ideas/<IDEA_ID>/runs and updates ideas/<IDEA_ID>/latest; optional patch if allowed)

Domain-specific testing patterns for episodic memory operations. Use when testing episode lifecycle, pattern extraction, reward scoring, or memory retrieval.

Epistemological tracking system for managing facts, conclusions, and provenance chains with Git integrity and semantic search. Integrates with Quarto for visual provenance analysis. Use when analyzing data from multiple sources, conducting research, working with metrics/surveys, making data-driven conclusions, or tracking complex findings. Triggers on data analysis (analyze data, metrics, survey, research, findings, insights), conclusions (conclude, recommend, decide, infer), quantitative work (percentage, trend, correlation, statistic), source attribution (according to, based on, from source), or any epistemological tracking. Skip for trivial calculations.

Discipline epistemique stricte pour eliminer les derives cognitives de Claude. Activation SYSTEMATIQUE sur TOUTES les conversations. Impose: (1) Zero invention/supposition, (2) Honnetete absolue, (3) Vision holistique avec relecture du contexte, (4) Questions plutot que suppositions, (5) Remise en contexte perpetuelle avec checkpoints structures, (6) Documentation incrementielle sans doublons, (7) Vigilance workflow/CI-CD/securite, (8) TODO/plan obligatoire avant tout travail, (9) Documentation FR/EN scholar style signee Julien GELEE, (10) Zero credentials/API keys/donnees sensibles en clair. Posture ingenieur generaliste specialise IA.

Master epistemology - the theory of knowledge, justification, and belief. Use for: knowledge, justification, skepticism, sources of knowledge, epistemic virtue. Triggers: 'knowledge', 'epistemology', 'justification', 'belief', 'Gettier', 'skepticism', 'certainty', 'evidence', 'testimony', 'perception', 'reason', 'a priori', 'empirical', 'reliability', 'internalism', 'externalism', 'foundationalism', 'coherentism'.

Discover and explore available eptr2 API endpoints for Turkish electricity market data. List all 213+ API calls, find endpoints by category (GÖP, GİP, DGP, Üretim, Tüketim), search for specific data types, and get parameter requirements. Use when asking what data is available, how to find endpoints, or exploring the API. Triggers on: available endpoints, API calls, list endpoints, what data, which API, how to find, hangi veri, mevcut servisler.

Run EPUBCheck and Ace accessibility validation. Use before final EPUB packaging or distribution to ensure publication readiness.

Expert in EqualizerAPO configuration file format, parsing, and generation. Use when implementing EAPO config import/export, adding support for new filter types, or debugging config file issues.

Use when you have validated symmetry groups and need to design neural network architecture that respects those symmetries. Invoke when user mentions equivariant layers, G-CNN, e3nn, steerable networks, building symmetry into model, or needs architecture recommendations for specific symmetry groups. Provides architecture patterns and implementation guidance.

Intelligent agent for interpreting vague ERPNext development requests and producing concrete technical specifications. Use when receiving unclear requirements like 'make invoice auto-calculate', 'add approval workflow', 'sync with external system'. Triggers: user gives vague requirement, need to clarify scope, translate business need to technical spec, determine which ERPNext mechanisms to use, create implementation plan.

Implementation workflows and decision trees for Frappe hooks.py configuration. Use when determining HOW to implement doc_events, scheduler_events, override hooks, permission hooks, extend_bootinfo, fixtures, and asset includes. Covers V16 extend_doctype_class. Triggers: how do I hook, which hook to use, doc_events vs controller, override doctype, extend doctype class, permission hook, scheduler job, cron task, fixtures export.

Implementation workflows and decision trees for Jinja templates in ERPNext/Frappe. Use when determining HOW to implement Print Formats, Email Templates, Portal Pages, or custom Jinja methods. Covers template type selection, context variables, styling, and V16 Chrome PDF rendering. Triggers: create print format, email template, portal page, custom jinja filter, print format styling, pdf template, invoice template, report template.

Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience. Masters error correlation, cascade prevention, and automated recovery strategies across multi-agent systems with focus on minimizing impact and learning from failures.

Context-aware debugging that learns from past solutions. When an error occurs:

Use when user needs complex error pattern analysis, distributed system debugging, error correlation, root cause discovery, or predictive error prevention across microservices.

Advanced error analysis and pattern detection specialist for identifying, analyzing, and preventing software errors

Evaluates if error handling is sufficient for new code - checks try-catch coverage, logging, user messages, retry logic. Focuses on external calls and user-facing code.

>

Expert in error handling, Error Boundaries, Sentry integration, logging strategies, error recovery, user-friendly error UI, and debugging tools

A guide to using ERT (Emacs Lisp Regression Testing) for testing Emacs Lisp code.

Query ESC (European Society of Cardiology) Guidelines by automatically locating the relevant PDF from the TOC and extracting cited answers. Use when answering clinical questions about cardiovascular diseases based on official ESC recommendations.

Use when stuck in circles and want to hand off to another agent (Codex CLI) with full context

Defining clear ownership models and escalation procedures to ensure incidents are handled by the right people at the right time.

Balance escape room difficulty, timing, and hint systems to achieve 60-70% completion rate. Designs progressive difficulty curves, three-tier hint systems, stuck-point analysis, and playtest metrics. Use when balancing game difficulty, designing hint systems, analyzing playtest data, or optimizing escape room completion rates.

Adapt escape room games for global markets (English, Korean, Japanese) with cultural considerations, efficient translation workflows, and language-agnostic design strategies. Handles multilingual template creation, cultural adaptation, and localization testing. Use when preparing games for international audiences or implementing multi-language support.

Use when eSLint configuration including config files, extends, plugins, and environment setup.

Use when custom ESLint rules and plugins including rule development, AST traversal, and publishing.

Use when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.

ESP32 Integrated Development Framework documentation. Covers I2S, GPIO, FreeRTOS, peripherals, and ESP32S3-specific APIs.

Specialist skill for ESP32-S3-BOX-3 hardware providing complete configuration templates, display lambda cookbook, touch interaction patterns, and voice assistant integration for complex audio/display/

ESS Technology MPN encoding patterns, high-end audio DAC decoding, and handler guidance. Use when working with ESS Sabre DACs or ESSHandler.

Canon de estilo narrativo para SyV - 13 reglas de construcción de prosa basadas en proporción áurea, elipsis emocional y sincretismo técnico-litúrgico

Listener agency preservation and non-coercive suggestion framework

Designs and implements Extract, Transform, Load pipelines for data processing

eval-recipes-runner

Git branch cleanup utility. Lists and deletes branches that have been merged to main. Use when user wants to clean up old branches, delete merged branches, or tidy up their git repository.

System for testing multi-agent behavior consistency across prompts, tools, skills, models, and agent configs.

EvalKit is a conversational evaluation framework for AI agents that guides you through creating robust evaluations using the Strands Evals SDK. Through natural conversation, you can plan evaluations, generate test data, execute evaluations, and analyze results.

Measure model performance on test datasets. Use when assessing accuracy, precision, recall, and other metrics.

Evaluate LLM systems using automated metrics, LLM-as-judge, and benchmarks. Use when testing prompt quality, validating RAG pipelines, measuring safety (hallucinations, bias), or comparing models for production deployment.

Two-stage paper screening - abstract scoring then deep dive for specific data extraction

Evaluate RAG systems with hit rate, MRR, faithfulness metrics and compare retrieval strategies. Use when testing retrieval quality, generating evaluation datasets, comparing embeddings or retrievers, A/B testing, or measuring production RAG performance.

Evaluate skills by executing them across sonnet, opus, and haiku models using sub-agents. Use when testing if a skill works correctly, comparing model performance, or finding the cheapest compatible model. Returns numeric scores (0-100) to differentiate model capabilities.

Evaluate agent systems with quality gates and LLM-as-judge. Use when you need to measure component quality or implement quality gates. Not for simple unit testing or binary pass/fail checks without nuance.

Build systematic evaluation frameworks for LLM applications.