Default perms
I run a one-person web design & development studio, specialising in complex custom WordPress build. Here are the claude skills I use daily to run it.
npx -y skills add markbain/bain-skills --skill default-permsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write default permissions to .claude/settings.json for the current project. Use when setting up a new project or when asked to add default permissions.
SKILL.md
1.2 KB, 254 tokens by cl100k_base, as published. Nobody here has run it
Default Permissions Skill
Write the standard default permissions to .claude/settings.json in the current project.
Step 1 — Check for existing settings
Check if .claude/settings.json already exists:
ls .claude/settings.json 2>/dev/null
If it exists, read it first so you can merge without overwriting unrelated keys.
Step 2 — Write permissions
Ensure the .claude/ directory exists:
mkdir -p .claude
Write (or merge) the following permissions into .claude/settings.json:
{
"permissions": {
"allow": [
"Bash(*)",
"Read(*)",
"Write(*)",
"Edit(*)",
"WebSearch(*)",
"WebFetch(*)",
"mcp__plugin_asana_asana__*"
]
}
}
If the file already exists, merge the allow array — add any missing entries from the list above without removing entries that are already there. Preserve all other existing keys.
Step 3 — Report
Confirm .claude/settings.json has been written and list the permissions now in the allow list.