Results for “output-enforcement”

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

Validate skill outputs against assertion manifests to detect regressions, enforce quality gates, and bootstrap starter manifests from historical runs.

Automated test validation, coverage checking, and quality metrics with aggressive defaults

Runs commands, inspects git state, debugs CI failures, and makes narrow fixes with exact proof of what was executed and verified.

Orchestrator for the eval-output skill suite — evaluate LLM and agent outputs for quality, accuracy, helpfulness, and safety using structured rubrics and LLM-as-judge techniques. Load when the user says "evaluate this output", "score this response", "run an eval", "LLM as judge", "evaluate agent output", "how good is this response", "rate this answer", "eval this", or provides an LLM output that should be assessed for quality. Single entry point for all output evaluation workflows.

Agent validation v4.3.0 — Make agents act effectively by disabling harmful actions, lowering gates, and injecting cross-run learning

Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.

Use this when a codebase or design effort needs consistency enforcement for tokens, spacing, typography, color usage, component variants, and reusable interaction patterns.

smart-output

整合智能体输出结果为结构化最终输出，支持多种格式。适用于整合分析报告、生成结构化报告

Outcome Eval

Executes terminal commands, inspects git state, debugs CI or builds, and makes narrow fixes with exact proof of what was executed and verified.

Parallel execution engine for high-throughput task completion

Augment the standard exec lifecycle with monorepo detection, lane-spec generation, guard validation, and package-scoped dispatch

6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk. Use when evaluating a third-party skill before installing, enabling, updating, publishing, or distributing it; reviewing an untrusted SKILL.md, agent configuration, MCP integration, archive, or repository; comparing a package with a known-good version; or investigating unexpected tool, network, credential, or filesystem behavior.

Restricts unauthorized removable media access on endpoints by implementing USB device control policies via Group Policy, Intune, or EDR platforms to prevent data exfiltration and malware introduction.

Manage teams using Andy Grove's principles: production thinking for knowledge work, output indicators, managerial leverage, effective meetings, clean decisions, OKRs, and task-relevant maturity.

Design, deploy, and operate production-ready software with stability patterns, capacity planning, and zero-downtime releases.

Ruthless team performance audits (Elon Algorithm) and meeting-to-action extraction. Use for performance audits, meeting action items, or org efficiency reviews.

Define owned inductive invariants and enforce them at parse, construct, API, DB, lock, or transaction boundaries, with counterexample-driven verification.

Use this skill for auth boundaries, input validation, secrets, RLS, injection risks, destructive-action review. Trigger when the task involves security work related to Security Hardening, production implementation, audits, debugging, strategy, or validation.

Executes commands, inspects git state, debugs CI or builds, makes narrow fixes, and reports exactly what changed and what was verified.

Deploy Llama Guard, NeMo Guardrails, and LLM Guard as runtime input/output scanners to block jailbreaks, prompt injection, and toxic content in production LLM applications.

Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.

Produces an evidence-backed inventory of live automations (jobs, hooks, connectors, MCP servers, wrappers) and recommends keep/merge/cut/fix-next actions before rewriting anything.

Executes containment strategies to stop active adversary operations and prevent lateral movement during a confirmed security breach, using network segmentation, endpoint isolation, credential revocation, and access control modifications.

Audit team performance using the Elon Algorithm (identify A/B/C players) and extract action items from meeting transcripts. Use when asked to "audit team performance", "review my team", "extract meeting actions", "meeting notes to tasks", "team efficiency audit", or "identify underperformers".

当需要系统性地提升工作专注度和生产力，实现高质量成果时

Organizes email triage, drafting, replying, and sending with verification that messages landed in the Sent folder.

Measures whether coding agents actually follow skills, rules, or agent definitions by generating test scenarios, running agents, and classifying tool calls to report compliance rates.

Default execution rhythm — inspect → act → verify → checkpoint — applied iteratively until the task is done or a clear blocker emerges. Use when working through a known plan, draining a queue (PRs, issues, dependency bumps), or executing a multi-step recipe where each step's output informs the next. Each iteration must produce a concrete artifact (commit, comment, decision) and a one-line state update. Stop on first unrecoverable error rather than retrying blindly. Pair with `ship` for merge-bound work and `handoff` if budget runs out mid-loop.

Composite skill — emergency bypass of the release branch when production is broken and waiting for the next release-cut is not viable. Chains incident scoping → branch from main (NOT release) → minimal fix → pr-merge-readiness → merge to main → patch-version tag → deploy → cherry-pick to release branch → post-deploy verify (sentry + ci-watch). Use ONLY for production-impacting breakage; routine "small fix" work belongs in /pr-to-release.

Adversarial dynamic e2e QA workflow - generate hostile scenarios, test, verify, fix, report, and clean up