CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

proof-orchestrator

Manage a stateful, run-directory-based proof project with Codex: continuation across runs, run-local source bookkeeping, manual GPT Pro handoff packages when a local attempt stalls, and an optional DeepSeek second opinion as additional evidence only. Use when the user asks for proof-run orchestration, a GPT Pro handoff, or cross-run proof continuation — use /proof-writer for ordinary proof drafting and /proof-checker for rigorous verification or submission acceptance.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable, well-sequenced orchestration protocol with concrete file layouts, templates, gates, and feedback loops. Its weaknesses are repeated restatement of the same guardrails across sections, which inflates length without adding information, and two orphaned bundle files that the body never points to.

Suggestions

State each authorization guardrail once (in Guardrails) and reference it from the Role section and workflow steps instead of restating the browser/API/DeepSeek authorization rules verbatim in three places each.

Reference references/dispatch-prompts.md and references/stress-tests.md at the relevant workflow steps (e.g., handoff preparation and external-review validation) so the bundle files are discoverable from SKILL.md.

Consolidate the duplicated notation-scorecard instructions: the Notation Gate section and workflow step 5 both restate the 'copy the exact seven-line scorecard, do not rename/merge' rule; keep one canonical statement and point to it.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows, but the same guardrails are restated repeatedly: the escalation-authorization rule appears in the Role section, workflow step 7, and Guardrails; 'DeepSeek only on explicit request' and 'additional evidence, not acceptance' each appear in three places. This is 'mostly efficient but could be tightened' rather than the minor-trim level of 4, though it avoids the padded-explanation profile of a 2.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: an exact run-directory file layout with per-file roles, an enumerated status-label set, a copy-paste seven-line scorecard, a concrete repair example ('\left{' to '\left\{'), and a distinctive output marker (END_GPT_PRO_OUTPUT). Specific templates and decision points cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with an explicit default route, status labels serving as checkpoints, two gates (Notation Gate, Derivation Structure Gate) with pass/fail criteria that block READY_FOR_USER, and error-recovery feedback loops (NEEDS_GPT_PRO_REDO with a focused redo prompt, AUDIT_FAILED, DEEPSEEK_REVIEW_BLOCKED). This matches the anchor for explicit validation steps with feedback loops.

5 / 5

Progressive Disclosure

Four reference files (notation-audit, proof-audit-rubric, deepseek-routing, audit-output-contract) are real, one level deep, and clearly signaled at the decision points where they are needed. However, two of the six bundle files — dispatch-prompts.md (227 lines) and stress-tests.md — are never referenced anywhere in the body, leaving them undiscoverable; that is a minor organization gap placing this at 'good structure' rather than the fully clear navigation of a 5.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities, gives an explicit 'Use when' clause with natural trigger phrases, and proactively disambiguates against sibling proof skills. The only weakness is that a few natural user phrasings (e.g., 'continue a proof', 'second opinion', 'DeepSeek review') are not covered in the trigger clause.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'continuation across runs, run-local source bookkeeping, manual GPT Pro handoff packages when a local attempt stalls, and an optional DeepSeek second opinion' — which comprehensively cover the skill's actions. This matches the anchor for multiple specific concrete actions with comprehensive coverage, and is above the 'minor gaps' level of 4.

5 / 5

Completeness

Both what and when are explicit: the capability list answers 'what does this do' and 'Use when the user asks for...' supplies concrete trigger phrases. This clearly matches the anchor for explicitly answering both with concrete triggers; a 4 would require the when to be less explicit, which it is not.

5 / 5

Trigger Term Quality

The when-clause gives three natural trigger phrases ('proof-run orchestration, a GPT Pro handoff, or cross-run proof continuation'), which is good coverage but omits common phrasings users would naturally say such as 'resume/continue a proof', 'second opinion', or 'DeepSeek review'. It fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (run-directory proof orchestration with escalation) and explicitly routes overlapping requests away: 'use /proof-writer for ordinary proof drafting and /proof-checker for rigorous verification or submission acceptance'. Minimal conflict risk, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/proof-orchestrator/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.