CtrlK
BlogDocsLog inGet started
Tessl Logo

team-rules

Apply the team's shared coding rules before writing, modifying, or reviewing code. Trigger when the user asks to add a feature, refactor, fix a bug, write tests, or review a change. Reads rules live from the team-rules MCP workspace at /rules/*.md.

76

Quality

95%

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

100%Weight 40%Scale 1-3

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

An exemplary instruction-only skill body: concise, immediately actionable with concrete tool calls and file paths, a clearly sequenced workflow with an explicit conflict checkpoint, and clean section organization appropriate to its size. Nothing is padded or inferred.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what an MCP server, a coding rule, or a filesystem workspace is, and each section earns its tokens; the intro establishes only the non-obvious read-only / single-source-of-truth constraints.

3 / 3

Actionability

Guidance is fully executable: a specific tool call with parameters ('Call mcp__team-rules__file_list with path: "/rules" and depth: 2'), concrete rule-file paths to read per situation, and a quick-reference table mapping situations to files — copy-paste ready, no pseudocode.

3 / 3

Workflow Clarity

The 'Before writing or editing code' section lays out a clear 4-step sequence (list → read applicable rules → cite in plan → apply), and the 'Rules of engagement' section adds an explicit conflict checkpoint ('surface the conflict and ask before deciding') plus a no-applicable-rule guard, providing the feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

At under 50 lines with no external bundle files (references/, scripts/, assets/ are absent) and a single focused purpose, the well-organized sections (intro, before-editing workflow, rules of engagement, quick-reference table) satisfy the simple-skill carve-out for a top progressive-disclosure score.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 well-crafted description that pairs a concrete capability statement with an explicit, natural-language trigger list and a distinct team-rules niche. Its only weakness is single-domain specificity — the actions described all serve one capability rather than a varied set.

DimensionReasoningScore

Specificity

Names concrete actions ('Apply the team's shared coding rules before writing, modifying, or reviewing code', 'Reads rules live from the team-rules MCP workspace') but they all serve a single domain capability rather than a breadth of distinct actions, so it sits at 'names domain and some actions' rather than the multiple-distinct-actions anchor.

2 / 3

Completeness

It explicitly answers both what ('Apply the team's shared coding rules... Reads rules live from the team-rules MCP workspace') and when ('Trigger when the user asks to add a feature, refactor, fix a bug, write tests, or review a change'), matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

The trigger clause enumerates natural phrasings users would actually say — 'add a feature, refactor, fix a bug, write tests, or review a change' — giving good coverage of common variations rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

The 'team's shared coding rules' framing tied to the team-rules MCP workspace carves a clear niche unlikely to collide with unrelated skills, matching the clear-niche anchor.

3 / 3

Total

11

/

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
redis/agent-filesystem
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.