Loading...
Loading...
Found 1,511 Skills
Validate Technical Specifications (SPEC) documents against Layer 9 schema standards
[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.
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Validates custom dotnet new templates for correctness before publishing. Catches missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes that cause templates to fail silently. USE FOR: checking template.json files for errors before publishing or testing, diagnosing why a template doesn't appear after installation, reviewing template parameter definitions for type mismatches and missing defaults, finding shortName conflicts with dotnet CLI commands, validating post-action and constraint configuration. DO NOT USE FOR: finding or using existing templates (use template-discovery), creating projects from templates (use template-instantiation), creating templates from existing projects (use template-authoring).
GANG skeptic skill. You act as the devil's advocate for orch, challenging orch's task breakdowns, VAL coverage, and progress assessments on critical decisions.
Six-phase protocol for adapting methods across research domains
Scan, assess, plan, and replace SaaS tools with AI-built code. Analyzes your codebase for SaaS integrations, generates migration plans, executes replacements, and validates results.
Write a deterministic OK file to out/ok.txt.
Generate lightweight section/subsection transitions (NO NEW FACTS) to prevent “island” subsections; outputs a transition map that merging/writing can weave in. **Trigger**: transition weaver, weave transitions, coherence, 过渡句, 承接句, 章节连贯性. **Use when**: `outline/subsection_briefs.jsonl` exists and you want coherent flow before/after drafting (typically Stage C5). **Skip if**: `outline/transitions.md` exists and is refined (no placeholders). **Network**: none. **Guardrail**: do not add new factual claims or citations; transitions may only refer to titles/RQs/bridge terms already present in briefs.
guide and workflow for rule-creation.