Loading...
Loading...
Found 2,944 Skills
Walk through a Jira task plan and interactively confirm assumptions, resolve open questions, and validate decisions — using progressive disclosure. Only asks questions relevant to the CURRENT phase or task being executed. Use when the user says "review the plan", "ask me questions", "clarify assumptions", "let's go through the questions", "grill me on the plan", "validate plan for PROJECT-1234", or anything about reviewing, questioning, or validating a task plan. Also triggered by the orchestrating-jira-workflow skill as Phase 3 of the pipeline, and re-invoked during Phase 5 before each task execution. Requires a task plan at docs/<TICKET_KEY>-tasks.md.
Parseur et explicateur complet du format HPK (format de message propriétaire santé). Supporte plus de 100 types de messages couvrant l'administration des patients (ID, MV, CV), la chaîne logistique (PR, FO, MA, CO, LI, RO, FA), les stocks (SO, IM), la structure organisationnelle (ST, UT) et les opérations financières (RD, DD). Utilise @erp-pas/hpk-dictionary comme source de vérité. Valide la structure, extrait les champs, explique le contexte métier, mappe vers HL7 v2.5/IHE PAM et aide au dépannage des problèmes d'intégration.
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
Standardize and validate SKILL.md files against the Agent Skills specification (agentskills.io). Use when creating new skills, auditing existing skills for spec compliance, converting legacy skill formats to standard structure, or improving descriptions for reliable triggering. Triggers on: "validate skill", "create SKILL.md", "standardize skill format", "check skill spec", "skill frontmatter", "improve skill description", "add evals to skill".
Verify that a change really works before you claim completion
Verify documentation coverage and generate missing docs interactively
Schedule and manage cron jobs. Use when: user needs to create, list, remove, or test scheduled tasks.
Adversarial stress-test of a /think intelligence brief. Reads the think output markdown, then deploys 5-7 of the same analytical frameworks — but each one is hunting exclusively for reasons the recommendation is wrong, the conviction is unearned, and the idea will fail. Every framework becomes a prosecutor, not a judge. Surfaces the strongest kill shots, identifies which parts of the original brief are load-bearing but unverified, and produces a Red Team Report with a survival verdict. Use when the user says "red-team this", "attack this", "poke holes", "steel-man the opposition", "why is this a bad idea", "/red-team", or presents a /think brief they want stress-tested.
Validate a Steedos package after creation or modification. Run this tool to check that all files conform to Steedos conventions: correct naming, required fields, valid enum values, proper file organization. TRIGGER: After creating or modifying files in a Steedos package (objects, fields, buttons, triggers, functions, listviews, permissions, apps, tabs, pages). Run before completing the task to catch issues early. SKIP: When only reading files, answering questions, or working outside a Steedos package context.
Use when an approved plan exists and needs execution, or when a hotfix/one-sentence scope needs direct TDD implementation — dispatches subagents per task, validates, reports
Validate a Claude Code plugin structure, frontmatter, and MCP tool references
[Hyper] Analyze vague or relayed non-developer stakeholder requests (client, executive, PM, sales/support) by mapping them to codebase impact, presenting interpretation candidates with risks, then implementing only after confirmation. Use for stakeholder-message analysis, not browser QA testing, CI/build failures, or already-clear technical tasks.