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.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/omo/components/rules/skills/rules/SKILL.md
SKILL.md
Quality
Evals
Security

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 tight, well-organized reference that respects the token budget and needs no external files; its only gap is that it presents configuration values as a listing rather than demonstrating how to apply them.

Suggestions

Add one short worked example showing a typical configuration, e.g. setting 'CODEX_RULES_MODE=static' with 'CODEX_RULES_ENABLED_SOURCES=CONTEXT.md,.omo/rules', to push actionability to level 3.

Briefly note how to verify rules are being injected (e.g. expected session-start behavior) so users can confirm configuration took effect.

DimensionReasoningScore

Conciseness

The body is lean — short bullets stating what is injected, the supported source paths, and the env knobs — with no padded explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

It lists concrete, copy-paste-ready values (e.g. 'CODEX_RULES_DISABLED=1', '.omo/rules/**/*.md'), but as a reference listing it gives no worked example or instruction applying them to a task, leaving the guidance concrete yet incomplete.

2 / 3

Workflow Clarity

This is a simple informational skill with no multi-step or destructive process; per the simple-skills note, its single purpose is conveyed unambiguously through well-ordered sections.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and its content is organized into clear sections, satisfying the simple-skills allowance for level 3.

3 / 3

Total

11

/

12

Passed

Description

72%

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

The description has a clear trigger clause and a distinct, well-scoped niche, but it describes topics rather than concrete actions and leaves the skill's actual capability implied rather than stated.

Suggestions

Lead with a concrete action verb for what the skill does (e.g., 'Explains Codex Rules behavior and configuration...') before the 'Use when' trigger.

Add a few concrete actions such as 'configure rule sources', 'tune environment knobs', or 'troubleshoot rule injection' to lift specificity to level 3.

DimensionReasoningScore

Specificity

Names the domain ('Codex Rules') and several specific sub-areas ('injected project rules, supported rule file locations, matching, or environment configuration'), but these are topics rather than concrete actions the skill performs, so it is not a comprehensive action list.

2 / 3

Completeness

The 'when' is explicit via 'Use when the user asks about...', but the 'what does this do' is only implied through the listed topics rather than stated as an action, so it falls short of the level-3 bar.

2 / 3

Trigger Term Quality

The 'Use when the user asks about...' clause supplies natural terms a user would say — 'Codex Rules', 'project rules', 'rule file locations', 'environment configuration' — giving good coverage of the domain.

3 / 3

Distinctiveness Conflict Risk

'Codex Rules' is a named, specific feature with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

10

/

12

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.