CtrlK
BlogDocsLog inGet started
Tessl Logo

rules

Use when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or environment configuration.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, well-organized reference skill that conveys concrete configuration facts without padding and assumes Claude's competence. The only gap is the absence of worked examples showing how to apply the environment knobs to a concrete scenario.

DimensionReasoningScore

Conciseness

A lean ~25-line reference that assumes Claude's competence, with no padding explaining what rules or environment variables are; every line is factual reference content that earns its place.

5 / 5

Actionability

Provides concrete, copy-paste-ready configuration facts (exact file globs like '.omo/rules/**/*.md' and env vars with value enums like 'CODEX_RULES_MODE=both|static|dynamic|off'), but offers no worked examples of applying them to a task.

4 / 5

Workflow Clarity

A single-purpose reference skill whose action (automatic injection once enabled) is stated unambiguously upfront, with content organized into clear categories; no destructive or batch operation requires validation checkpoints.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files; content is well-organized into clearly signaled sections (injects, sources, env knobs, legacy) with no nested references.

5 / 5

Total

19

/

20

Passed

Description

73%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 trigger-focused description with a clear explicit 'Use when' clause and distinct, niche-specific terms. Its main weakness is the absence of an explicit action statement, framing capabilities as topics to ask about rather than concrete actions performed.

Suggestions

Lead with an explicit action statement of what the skill does (e.g., 'Injects and matches project rules for Codex'), then follow with the 'Use when...' clause to clearly answer both 'what' and 'when'.

Convert topic nouns into concrete verbs (e.g., 'injects project rules', 'matches file-specific rules', 'configures rule sources') to lift specificity from topics to actions.

DimensionReasoningScore

Specificity

Lists several specific facets (Codex Rules behavior, injected project rules, rule file locations, matching, environment configuration), but these are topics the user 'asks about' rather than concrete actions the skill performs, with no explicit 'what' verb.

3 / 5

Completeness

Has an explicit, specific 'Use when...' trigger clause with concrete triggers, and the topic list conveys the 'what' (project-rule injection/matching/configuration) even though no action verb states it directly.

4 / 5

Trigger Term Quality

Good coverage of natural phrases a user would say ('Codex Rules behavior', 'project rules', 'rule file locations', 'environment configuration') with several relevant synonyms, missing only minor variations.

4 / 5

Distinctiveness Conflict Risk

The 'Codex Rules' proper noun plus specific triggers (rule file locations, environment configuration) carve a clear niche with minimal conflict risk against other skills.

5 / 5

Total

16

/

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