CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-rules

Add project-specific rules and conventions to the configured RULES.md artifact. Each invocation appends new rules. These rules are automatically loaded by /aif-implement before execution. Use when user says "add rule", "remember this", "convention", or "always do X".

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 ./skills/aif-rules/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The core workflow is highly actionable with templates, exact paths, and clear mode routing, but the skill carries substantial inline policy padding: the runtime-aware question contract and duplicated precedence explanations roughly double the length needed. Splitting or trimming the policy sections and adding a post-edit verification step would raise both conciseness and workflow clarity.

Suggestions

Move the "Runtime-aware questions" interaction contract into a shared reference file (or compress it to 3-4 bullets) — it is generic policy, not skill-specific instruction, and accounts for ~20 lines of the body.

State the skill-context precedence rules once: "Step 0.1: Load Skill Context" repeats the conflict/priority guidance already given in "Shared project skill-context" — merge them into a single section.

Trim the Step 0 language handling to the resolution chain plus one fallback line; the exhaustive enumeration of legacy/invalid technical_terms_policy values is unlikely to occur and can be cut.

DimensionReasoningScore

Conciseness

Noticeably verbose for a rule-appending skill: the ~20-line "Runtime-aware questions" contract restates the same constraints (don't guess tools, fall back to plain text, silence is not consent) in multiple dense bullets, and precedence rules are explained twice — once in "Shared project skill-context" and again in "Step 0.1". Not 1 because it never explains concepts Claude already knows; all padding is procedural policy, but there are several padded/redundant sections.

2 / 5

Actionability

Fully executable for an instruction-only skill: copy-paste-ready markdown templates for RULES.md and area files, exact default paths, tool-specific steps (Glob existence checks, Edit appends, config.yaml registration), a mode-routing decision tree, and worked invocation examples (/aif-rules area:api). All common cases are covered concretely.

5 / 5

Workflow Clarity

Clear sequence (Step 0 config → 0.1 skill context → mode routing → read/create → append → confirm) with existence checks before create-vs-append, a duplicate check, explicit STOP after Mode C, and confirmation output with counts. Not 5 because there is no explicit post-edit verification (re-read the file) or error-recovery loop for a failed append.

4 / 5

Progressive Disclosure

Good section headers and organized steps, but ~50 lines of generic policy (runtime-aware questions, skill-context precedence) are inlined rather than split into reference files, and the body refers to "its linked references" even though no reference files exist in the bundle. Fits the some-structure/could-be-better-organized anchor, above the minimal-structure anchor at 2.

3 / 5

Total

14

/

20

Passed

Description

83%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 description: third-person, concrete about the what (append rules to the configured RULES.md artifact, auto-loaded by /aif-implement), and explicit about when with quoted user trigger phrases. Only minor gaps — a few missing trigger synonyms and no mention of the area-rules capability.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Add project-specific rules and conventions to the configured RULES.md artifact", "Each invocation appends new rules", "automatically loaded by /aif-implement before execution" — with named artifacts. Not 5 because major capabilities (area rules, three-level hierarchy) are unmentioned; not 3 because it goes beyond 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both what ("Add project-specific rules... appends new rules... loaded by /aif-implement") and when ("Use when user says 'add rule', 'remember this', 'convention', or 'always do X'") with concrete trigger phrases. Clearly matches the top anchor, not the weaker-'when' anchor at 4.

5 / 5

Trigger Term Quality

Quoted natural user phrases "add rule", "remember this", "convention", "always do X" are exactly what a user would say. Not 5 because common synonyms like "guideline", "policy", "standard", or "best practice" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (project rules in the AI Factory RULES.md/config.yaml ecosystem referenced by /aif-implement) with distinct triggers. Not 5 because "remember this" overlaps with memory/remember-type skills; not 3 because the RULES.md artifact framing is largely unique.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-rules/SKILL.md

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.