CtrlK
BlogDocsLog inGet started
Tessl Logo

lcx-contribute-bug-fix

Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.

72

Quality

89%

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

85%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-sequenced workflow with strong validation feedback loops for a risky batch operation. The main weakness is progressive disclosure: substantial inlined bash and templates that belong in separate files weigh down the overview.

Suggestions

Move the valid_source_checkout/recover_corrupt_source_checkout/sync_latest_source bash block into a bundled script (e.g. scripts/sync-sources.sh) and call it from the body, leaving only the one-line invocation inline.

Extract the Verified-Fix Issue Template and PR Body Template into reference files (e.g. references/issue-template.md, references/pr-body-template.md) and link to them, keeping a short summary of each in SKILL.md.

Consolidate the repeated 'never a PR against code-yeongyu/lazycodex' guidance into one authoritative Stop Conditions entry to reduce redundancy.

DimensionReasoningScore

Conciseness

Dense and operational with no padding about concepts Claude already knows, though the 'never a PR' emphasis is repeated several times and the source-sync helper block is lengthy enough that it could be trimmed or factored out.

4 / 5

Actionability

Fully executable copy-paste-ready bash for both target repos, a real bundled generator script with a concrete JSON input shape, and specific examples covering the common fork-PR and issue cases.

5 / 5

Workflow Clarity

A clear 13-step sequence with explicit validation checkpoints (failing-before test, passing-after test, real-surface QA, status inspection before commit, corrupt-checkout recovery) plus a Stop Conditions and 'Do not open' checklist for this destructive/batch workflow.

5 / 5

Progressive Disclosure

Good section structure and one correctly-referenced bundle script, but large inline blocks (the ~40-line source-sync helpers and both full delivery templates) are content that would be better placed in separate reference or script files rather than the overview.

3 / 5

Total

17

/

20

Passed

Description

95%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, third-person description that clearly states what the skill does and when to use it, with rich natural trigger phrases and a distinct niche. Minor specificity gap is the only thing keeping it from being perfect.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Contribute a verified bug fix', 'Opens a fork PR', 'become a verified-fix issue') tied to a named domain, with only minor coverage gaps around the investigation/debugging action itself.

4 / 5

Completeness

Explicitly answers both what (contribute a verified fix via fork PR or verified-fix issue, with ownership routing) and when (a 'Use when...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and variants ('fix a bug', 'contribute a bug fix', 'contribute to fix bug', 'open a PR for a bug', 'debug and PR a LazyCodex/Codex defect') that users would actually say.

5 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (LazyCodex/Codex bug-fix contribution with repo-specific routing) with distinct triggers and minimal overlap risk with other skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
code-yeongyu/lazycodex
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.