install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/feat-20260128-001720" ~/.claude/skills/majiayu000-claude-skill-registry-feat-20260128-001720 && rm -rf "$T"
manifest:
skills/data/feat-20260128-001720/SKILL.mdsource content
Remove block-commands skill
Overview
The
block-commands skill documents how to use .claude/settings.json deny rules to block dangerous commands. However, .claude/settings.json is a repository-local file that is not distributed with plugins. Users installing the plugin would not get these deny rules, making this approach ineffective for a marketplace plugin.
The skill should be removed since it documents a pattern we no longer recommend for plugin distribution.
Key Files
- Skill to deleteplugins/core/skills/block-commands/SKILL.md
Related History
The block-commands skill was created alongside moving git prohibitions to settings.json, but this approach has proven unsuitable for distributed plugins.
Past tickets that touched similar areas:
- Created block-commands skill and moved git -C prohibition to settings.json (same file)20260127094857-use-deny-for-git-prohibition.md
Implementation Steps
-
Delete block-commands skill directory:
- Remove
entirelyplugins/core/skills/block-commands/
- Remove
-
Verify no references exist:
- Confirm no other files reference
skillblock-commands
- Confirm no other files reference
Considerations
- This removes documentation only, not actual functionality
- The
deny rules remain in local repositories but are not part of plugin distribution.claude/settings.json - For plugin-based command blocking, bundled shell scripts that refuse to execute are more appropriate (as done with archive-ticket)
Final Report
Deleted the block-commands skill directory. Verified that no other plugin files reference this skill. Documentation in .workaholic/specs/ and .workaholic/terms/ will be updated automatically by the documentation agents when /report runs.