CtrlK
BlogDocsLog inGet started
Tessl Logo

debug

Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

83

1.00x
Quality

78%

Does it follow best practices?

Impact

83%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/debug/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A highly actionable, well-structured debugging runbook with concrete commands and validation steps. Its main weakness is conciseness: the same tracing workflow is presented three times across Quick Triage, Investigation Flow, and Reading Codex Session Logs.

Suggestions

Consolidate Quick Triage, Investigation Flow, and Reading Codex Session Logs into a single canonical sequenced workflow, with the Codex session lifecycle framed as a sub-section rather than a separate top-level retracing of the same steps.

De-duplicate the repeated 'pair session findings with issue_identifier/issue_id' guidance into one stated rule rather than restating it at the end of multiple sections.

If the detailed command catalog or the Codex session lifecycle reference grows, move it into a references/ bundle file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence (no explaining what rg or logs are), but Quick Triage, Investigation Flow, and Reading Codex Session Logs retrace the same workflow with repeated pair-with-identifier guidance, so it could be tightened.

3 / 5

Actionability

Copy-paste-ready `rg` commands with real patterns (e.g. 'session_id=[^ ;]+', 'Issue stalled|scheduling retry|turn_timeout') cover the five common debugging cases.

5 / 5

Workflow Clarity

Numbered sequences with explicit validation ('Validate scope', 'confirm you are not mixing concurrent retries') and feedback ('If noise is high, add issue_id'); minor gap from three overlapping flows creating ambiguity about the canonical path.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled one-level external reference (elixir/docs/logging.md) and no nested references; all content is inline with minor redundancy rather than split into bundle files.

4 / 5

Total

16

/

20

Passed

Description

82%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 tight, well-structured description that clearly states both capability and trigger conditions for a specific debugging niche. The only soft spot is specificity, since the concrete action set is essentially 'trace logs' rather than a broad list of operations.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers'), but the action set is narrow rather than comprehensive.

3 / 5

Completeness

Explicitly answers both what (tracing Symphony/Codex logs with issue/session identifiers) and when ('use when runs stall, retry repeatedly, or fail unexpectedly') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user-facing triggers are present ('use when runs stall, retry repeatedly, or fail unexpectedly'), with good but not exhaustive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to Symphony/Codex log tracing with issue/session identifiers, giving it a clear niche and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/symphony
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.