Permissions Debug logo

Permissions Debug

OrganizationPopular
shareAI-lab
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.

Overview

PublishershareAI-lab
RepositoryKode-CLI
Skill namepermissions-debug
Stars
5.2K
Forks
771
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by shareAI-lab on GitHub. Read the source before you install it.

Installation

Install the Permissions Debug AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/shareAI-lab/Kode-CLI.git /tmp/Kode-CLI
mkdir -p .claude/skills
cp -r /tmp/Kode-CLI/packages/builtin-skills/skills/permissions-debug .claude/skills/permissions-debug
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Permissions Debug in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Permissions Debug on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Permissions Debug is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Permissions Debug (Kode-first, fail-closed)

Non-negotiables

  • Do not auto-escalate permissions. If an action would normally require user approval, keep it interactive and explain why.
  • Prefer minimal, reversible permission changes and verify immediately.
  • In dontAsk contexts, treat “would prompt” as deny (fail-closed). Do not try to bypass.

Fast triage (what to check first)

  1. Confirm what is blocked

    • Look for the exact tool name and the rejection message.
    • If the failure is from a subagent, confirm whether the parent context was more restricted.
  2. Inspect approved tools / project allowlist

    • Use SlashCommand to run /approved-tools list and confirm whether the tool (or its rule category) is present.
    • If the list is unexpectedly long or contains stale entries, remove only the minimum needed with /approved-tools remove <tool>.
  3. Check per-command constraints

    • Some flows apply commandAllowedTools constraints (slash command / skill execution contexts). Confirm the command’s allowed-tools frontmatter and whether it should be restrictive.

Verification loop (keep it tight)

  • Re-run the exact action that was blocked and confirm:
    • whether the prompt appears (interactive modes), or
    • whether the tool is allowed/denied deterministically (headless / dontAsk).

Forensics (when “it should have worked”)

  • Inspect the latest session artifacts under ~/.kode/ (messages + errors) to confirm what tool call was attempted and why it was denied.
  • If a background shell was involved, cross-check task output files in ~/.kode/**/tasks/ for the corresponding bashId.

Frequently asked questions

What does the Permissions Debug AI skill do?

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.

Why use Permissions Debug on TypingMind?

Because you install it once and use it with any model. Permissions Debug is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Permissions Debug in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/shareAI-lab/Kode-CLI/tree/main/packages/builtin-skills/skills/permissions-debug. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Permissions Debug?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Permissions Debug?

As many as you like. As long as a model supports skills, you can use Permissions Debug with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Permissions Debug AI skill free?

Yes. It is published on GitHub by shareAI-lab under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇