AI agent configuration policy and security guide. Project description file writing, Hooks/Skills/Plugins setup, security policy, team shared workflow definition.
67
48%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/agent-configuration/SKILL.mdProject description file structure and conciseness
Tech Stack section
100%
100%
Coding Standards section
87%
100%
DO NOT section
50%
100%
Common Commands section
87%
100%
Bullet-point style
92%
100%
No verbose prose
100%
100%
No .env commit rule
100%
100%
No API key hardcoding rule
100%
100%
TypeScript strict mode
100%
100%
Project heading
42%
100%
Conciseness rationale
100%
100%
Security hooks configuration with correct patterns and actions
Top-level hooks key
100%
100%
PreToolUse event type
100%
100%
rm -rf / blocked
100%
100%
rm -rf /* blocked
100%
100%
curl | sh blocked
100%
100%
sudo rm warned not blocked
100%
100%
chmod 777 warned not blocked
100%
100%
Each rule has message
37%
100%
cc-safe mentioned
0%
100%
Block vs warn rationale
100%
100%
Valid JSON structure
100%
100%
Team configuration sharing and multi-agent skills directory
team-settings.json permissions.allow
100%
100%
team-settings.json permissions.deny
100%
100%
mcpServers placeholder
100%
100%
.agent-skills directory
100%
100%
agent-skills subdirectories
100%
100%
Gemini config file named
0%
100%
Cursor config file named
100%
100%
Claude config files named
100%
100%
.claude/ committed to Git
100%
100%
hooks in team-settings.json
100%
100%
Bash allow entries use correct format
100%
100%
No hardcoded secrets
100%
100%
fd18296
Table of Contents
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.