lcx-report-bug

Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

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

A thorough, highly actionable bug-routing skill with clear workflow sequencing and validation checkpoints. Its main weakness is length: the heavy inline shell scaffolding and repeated routing guidance could be externalized for better progressive disclosure and conciseness.

Suggestions

Move the source-sync shell block (valid_source_checkout/recover_corrupt_source_checkout/sync_latest_source) into a scripts/ file (e.g. sync_sources.sh) and reference it, reducing inline bulk.

Extract the Issue Body and PR Body templates into references/ files linked from the body, improving progressive disclosure one level deep.

Consolidate the repeated LazyCodex-vs-openai/codex routing rules (stated in Goal, Required Workflow step 6, and Stop Conditions) into a single authoritative decision section.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and evidence-bound, but the large inline source-sync shell block (valid_source_checkout, recover_corrupt_source_checkout, sync_latest_source) plus repeated routing rules and verbose stop-conditions could be tightened or pushed to a reference.	2 / 3
Actionability	Provides fully executable, copy-paste-ready shell commands (gh issue create, label create, source sync) and concrete templates with exact placeholders, meeting the bar for copy-paste-ready guidance.	3 / 3
Workflow Clarity	An explicit numbered workflow with validation checkpoints (validate cached checkouts, confirm root cause by observing failing state, search existing issues before creating, check both source trees before routing) and clear stop conditions for error recovery.	3 / 3
Progressive Disclosure	Well-organized into sections but everything lives in one monolithic SKILL.md with no external reference files, and the sizable source-sync script and templates are inline rather than split out one level deep.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, specific description that clearly states both the action and the trigger conditions, with natural trigger terms and a distinct niche. It is comprehensive without being padded.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create a high-signal bug issue or PR', 'source-backed root cause, reproduction steps, fix guidance, and GitHub routing') rather than vague abstractions.	3 / 3
Completeness	Explicitly states both what it does ('Create a high-signal bug issue or PR') and when to use it ('Use this whenever the user asks to report, file, open, or triage...'), satisfying the 'what AND when' requirement.	3 / 3
Trigger Term Quality	Covers natural user phrasings — 'report, file, open, or triage' — plus specific product names (LazyCodex, lazycodex-ai, omo-codex, Codex plugin, Codex CLI) that users would actually name.	3 / 3
Distinctiveness Conflict Risk	The narrow product-specific routing niche (LazyCodex vs openai/codex bug filing) is distinct and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: code-yeongyu/lazycodex
Path: plugins/omo/components/lcx/skills/lcx-report-bug/SKILL.md
Commit: 895b70c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.