Skip to content

docs: describe the permissions the guardrails skill needs - #6

Open
fwereade wants to merge 1 commit into
mainfrom
fwereade/docs/permissions
Open

fwereade wants to merge 1 commit into
mainfrom
fwereade/docs/permissions

Conversation

@fwereade

@fwereade fwereade commented Nov 4, 2026

Copy link
Copy Markdown

what

Adds a short "Permissions" section to the README, replacing the two paragraphs about approving
python3. It covers four things. On the Stacklet side, the skill only runs GraphQL queries through
platform_graphql_query and writes nothing to the platform. In Claude Code, users approve the MCP
query tool, the bundled scripts and temp-file writes, and choose their own permission rules; a
background sync that is denied a tool hands the sync back to the main session. It says where the
cache and the committed scope file live. And it says the nested claude -p calls spend the user's
own tokens, with a pointer to references/inference.md for using another tool.

why

Users had no single place that said what the skill touches and what they'll be asked to approve.

testing

Docs only; just lint passes.

docs

This is the docs change.

Stacklet access is read-only GraphQL; Claude Code asks to approve the MCP
query tool, the bundled scripts and temp files, and users write their own
rules; the cache and scope file locations; and nested `claude -p` calls
spending the user's tokens.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fwereade
fwereade requested a review from a team as a code owner November 4, 2026 17:40

@ajkerrigan ajkerrigan left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Useful info to have in one spot, thanks @fwereade 🍻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants