no-cutting-corners

Enforce five quality pillars before enumerated outputs or done claims.

Updated May 14, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skills --skill no-cutting-corners
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-cutting-corners
Source: https://github.com/jacob-balslev/skills/tree/main/skills/meta-methods/no-cutting-corners
Command: npx skills add https://github.com/jacob-balslev/skills --skill no-cutting-corners

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

No-cutting-corners provides an enforcement gate that ensures every enumerated output is complete, verified, and enriched before delivery, preventing silent scope reduction and unverified claims.

Core Features & Use Cases

  • Enforces the five pillars: completeness, verification, thoroughness, enrichment, and anti-shortcut.
  • Acts as a gate before any enumerated output, any "done" claim, or any "improve" task.
  • Useful when auditing enumerated outputs, when a claim lacks evidence, or when findings must be acted on.

Quick Start

List every finding first, then optionally flag items for deprioritization.

Frequently Asked Questions about no-cutting-corners

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce output completeness verification before returning enumerated results?

Enforce output completeness verification by applying a gate that validates five quality pillars—completeness, verification, thoroughness, enrichment, and anti-shortcut—before any enumerated output is delivered. This prevents silent scope reduction and unverified claims.

What is the best way to prevent silent scope reduction when auditing enumerated outputs?

The best way to prevent silent scope reduction is to use a deterministic enforcement gate that counts items, splits findings, and verifies each item with evidence before reporting results. This ensures thoroughness across all enumerated outputs.

How do I verify each item with evidence when handling findings or claiming a task is done?

Verify each item with evidence by enforcing an anti-shortcut gate that blocks any "done" claim or finding handling until deterministic checks confirm verification, thoroughness, and enrichment across the complete item count.

Does this output quality gate require specific dependencies to work across different project runtimes?

No, this output quality gate requires no specific dependencies. It is portable across projects and runtimes, validating completeness and verification deterministically before reporting results in any environment.

How do I expand output when improving artifacts under strict thoroughness checks?

Expand output when improving artifacts by passing through a thoroughness and enrichment gate that defines explicit rules for splitting findings and verifying each item with evidence before allowing any improvement task to complete.