skills.rest
samwelmunga
samwelmungaCOMMUNITY
Explore all skills by this author →
GitHub

j.jenga-permission-level

Report or switch the session's five-tier permission level via template-backed settings overwrites.

Updated Aug 3, 2026
Search Tags:#access control#configuration management#settings.json#agent permissions#session configuration#permission level#jenga ai
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-jenga-permission-level-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.jenga-permission-level
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/jenga-permission-level
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-jenga-permission-level-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing agent permission levels by hand-editing settings.json is error-prone and inconsistent. This Skill lets you check or change the current session's permission level (1 Locked through 5 Unrestricted) with a single command, keeping .claude/settings.json and .agents/settings.json in sync. ## Core Features & Use Cases - Status Reporting: Run without arguments to see the current session level read from .jenga-permission-level.json, always shown alongside the conceptual default of 2. - Validated Switching: Pass a level 1-5; invalid input (non-numeric, 0, 6+, decimals) is rejected before any file changes occur. - Script-Delegated Switching: A dedicated switch script copies the matching level template over both settings files as a whole-file overwrite and records the new session level. - Use Case: Before letting an agent run broad edits, switch to level 4 (Elevated), then lock back down to level 1 when the session's risky work is done. ## Quick Start Ask the agent to switch the session to permission level 4, or ask what permission level the session is currently at.

Frequently Asked Questions about j.jenga-permission-level

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the current permission level of my agent session?▼

Run the skill with no argument. It reads .jenga-permission-level.json at the repo root and prints the session level alongside the default, for example "Default: 2 / Session: 4". A missing or unparseable file is treated as level 2.

How do I change the agent permission level without editing settings.json?▼

Pass a level number from 1 to 5 as the argument. The skill validates the input, then delegates to the jenga-permission-level-switch.sh script, which copies the matching level template over both settings files and records the new session level.

What are the five permission levels in Jenga AI?▼

The levels are 1 Locked, 2 Guarded, 3 Standard, 4 Elevated, and 5 Unrestricted. Level 2 is the conceptual default and is always reported as the default regardless of the current session level.

What happens if I pass an invalid permission level like 0 or 6?▼

The skill validates the argument against the pattern ^[1-5]$ before doing anything. Invalid input such as 0, 6, decimals, or non-numeric values produces an error message and no file changes are made.

Does switching permission levels merge or overwrite settings.json?▼

It performs a whole-file overwrite of both .claude/settings.json and .agents/settings.json from the level template, not a merge. Top-level keys present in the destination but absent from the template are silently dropped, so templates must stay in sync.

Why does the permission switch fail with a missing script error?▼

The switch logic lives in scripts/jenga-permission-level-switch.sh or the node_modules fallback path. If neither exists, the skill reports a missing dependency rather than reimplementing the logic inline.

Related Skills

Explore More Software Engineering Skills→
openkaidenopenkaiden
10

working-with-podman-runtime-config

Generate dynamic Containerfiles and sudoers for Podman runtime configurations.

Official
Advanced
xxihxxih
1

executing-plans

Execute written implementation plans with step-by-step verified tasks.

Community
Advanced
archibatearchibate
37

explanatory

Switch output style to provide educational codebase insights during reviews and debugging.

Community
Intermediate
Oruga420Oruga420

psmux

Toggle the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS flag in ~/.claude/settings.json.

Community
Intermediate