CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-configuration

AI agent configuration policy and security guide. Project description file writing, Hooks/Skills/Plugins setup, security policy, team shared workflow definition.

67

1.13x
Quality

48%

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent-skills/agent-configuration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

32%

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 identifies a clear domain (AI agent configuration) and lists relevant capability areas, but suffers from lack of explicit trigger guidance and somewhat abstract action descriptions. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill from a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when setting up Claude Code projects, configuring agent permissions, creating AGENTS.md files, or defining MCP tool access policies'

Include more natural user terms such as 'Claude configuration', 'agent permissions', 'AGENTS.md', 'CLAUDE.md', 'MCP servers', or 'tool restrictions'

Make actions more concrete by specifying outputs like 'create AGENTS.md files', 'define hook scripts', 'configure allowed/disallowed tools', 'set up permission boundaries'

DimensionReasoningScore

Specificity

Names the domain (AI agent configuration) and lists several actions (project description file writing, Hooks/Skills/Plugins setup, security policy, team shared workflow definition), but these are somewhat vague categories rather than concrete specific actions like 'create hook files' or 'define permission boundaries'.

2 / 3

Completeness

Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. There is no indication of when Claude should select this skill over others.

1 / 3

Trigger Term Quality

Includes some relevant terms like 'Hooks', 'Skills', 'Plugins', 'security policy', and 'workflow', but misses common natural language variations users might say such as 'Claude configuration', 'agent setup', 'AGENTS.md', 'permissions', or 'MCP'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'AI agent configuration' with 'Hooks/Skills/Plugins' provides some distinctiveness, but terms like 'security policy' and 'workflow definition' are generic enough to potentially overlap with other configuration or documentation skills.

2 / 3

Total

7

/

12

Passed

Implementation

64%

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

This skill provides comprehensive, actionable guidance for AI agent configuration with good concrete examples and executable code. However, it's overly long for a SKILL.md file, mixing overview content with detailed reference material that should be split into separate files. The workflow sections lack explicit validation steps for potentially risky configuration changes.

Suggestions

Add explicit validation steps after hook configuration changes (e.g., 'Test hook with a safe command before relying on it for security')

Split detailed configurations (hooks JSON, team-settings.json) into separate reference files and link to them from the main skill

Remove explanatory text like 'Project description files are project manuals for AI' - Claude understands the concept

Add a feedback loop for security setup: 'After configuring hooks, run `cc-safe` to verify coverage, fix gaps, re-run until clean'

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some unnecessary explanations (e.g., 'Project description files are project manuals for AI') and could be tightened. The comparison tables and some verbose sections add bulk without proportional value.

2 / 3

Actionability

Provides concrete, executable examples throughout: JSON configurations, bash commands, directory structures, and complete code blocks that are copy-paste ready. The hooks configuration and team-settings.json examples are fully actionable.

3 / 3

Workflow Clarity

Steps are listed but lack explicit validation checkpoints. The 'Team Sharing Workflow' is oversimplified, and security setup checklist lacks verification steps. No feedback loops for error recovery in multi-step processes like hook configuration.

2 / 3

Progressive Disclosure

Content is organized into clear sections with headers, but it's a monolithic document that could benefit from splitting detailed configurations (hooks, team settings) into separate reference files. No external file references for advanced topics.

2 / 3

Total

9

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
supercent-io/skills-template
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.