AGENT SKILL

uninstall

Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

License 许可
MIT
所属仓库
agisota/old-one
最近更新
2026-07-04
Stars
★ 3
Forks
1

01 前言 Front Matter

name
uninstall
description
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.
argument-hint
[skill name]

03 SKILL.md 正文

/uninstall

Run the uninstall workflow from the skill-manager reference skill against the named skill.

Safety rules:

  1. Only uninstall community skills installed through this hub. Check ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml and the CLAUDE.md installed starter pack table. If the skill is not recorded there, refuse and tell the user.
  2. Never uninstall a first-party plugin's skill. The 12 core plugins that ship with claude-for-legal are off-limits from this command. If the named skill resolves to a path inside one of those plugins, refuse.
  3. Confirm before removing files. Show the user every path that will be deleted. Proceed only on explicit yes.
  4. Log the uninstall. Append to install-log.yaml with action uninstall and timestamp so the audit trail is intact.

If the user wants to stop a skill from running but keep the files (e.g., for later re-enable, or to preserve configuration), suggest /legal-builder-hub:disable instead.

Detailed uninstall, disable, and re-enable workflows live in the skill-manager reference skill — load it before doing substantive work.

04 同仓库更多 Skills

agisota
agisota/old-one

zoom-out

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

★ 3
agisota
agisota/old-one

zeroize-audit

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

★ 3
agisota
agisota/old-one

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 3
agisota
agisota/old-one

yara-rule-authoring

Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.

★ 3
agisota
agisota/old-one

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 3
agisota
agisota/old-one

x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

★ 3