CtrlK
BlogDocsLog inGet started
Tessl Logo

permissions-debug

Troubleshoot Kode permission prompts/denials (tool allowlists, commandAllowedTools, dontAsk fail-closed, subagent inheritance). Use when tools are unexpectedly blocked, permission prompts repeat, or behavior differs between main agent and subagents.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-organized debugging playbook with concrete commands, an explicit verification checkpoint, and no wasted tokens. It fully satisfies the content rubric for a simple instruction-only skill.

DimensionReasoningScore

Conciseness

The body is lean and every line earns its place — 'Do not auto-escalate permissions', 'treat would prompt as deny (fail-closed)' — with no padding and no explanation of concepts Claude already knows, matching the level-3 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete, executable guidance: real slash commands ('/approved-tools list', '/approved-tools remove <tool>'), a named frontmatter field ('allowed-tools'), and specific paths ('~/.kode/', '~/.kode/**/tasks/'), which is copy-paste-ready direction for an instruction-only debug skill.

3 / 3

Workflow Clarity

The 'Fast triage' is a clearly numbered 1-2-3 sequence and the 'Verification loop' is an explicit checkpoint ('Re-run the exact action that was blocked and confirm'), providing the feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

At under 50 lines with no external bundle files, the content is split into well-signaled sections (Non-negotiables, Fast triage, Verification loop, Forensics), which per the simple-skills note earns a 3 without external references.

3 / 3

Total

12

/

12

Passed

Description

75%

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 clearly communicates a distinct niche and includes an explicit 'Use when...' trigger, answering both what and when. It is slightly held back by a single abstract action verb and trigger terms that lean technical rather than colloquial.

Suggestions

Decompose 'Troubleshoot' into two or three concrete actions (e.g., 'Inspect, adjust, and verify tool allowlists') to lift specificity.

Add common natural-language trigger variants such as 'permission denied', 'tool blocked', or 'command not allowed' alongside the technical jargon.

DimensionReasoningScore

Specificity

It names the domain ('Kode permission prompts/denials') and enumerates concrete subsystems ('tool allowlists, commandAllowedTools, dontAsk fail-closed, subagent inheritance'), but the only action verb is the single abstract 'Troubleshoot' rather than a list of distinct concrete actions, so it falls short of the level-3 anchor.

2 / 3

Completeness

It states both what it does ('Troubleshoot Kode permission prompts/denials...') and an explicit when ('Use when tools are unexpectedly blocked, permission prompts repeat, or behavior differs between main agent and subagents'), matching the level-3 anchor with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Natural phrases like 'permission prompts', 'tools are unexpectedly blocked', and 'permission prompts repeat' are present, but the trigger set leans on technical jargon ('dontAsk fail-closed', 'commandAllowedTools', 'subagent inheritance') and misses common variations a user might actually say such as 'permission denied' or 'tool blocked'.

2 / 3

Distinctiveness Conflict Risk

The Kode permission-debugging niche is sharply defined with distinct triggers (tool blocking, repeating prompts, main-vs-subagent behavior divergence), 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
shareAI-lab/Kode-CLI
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.