AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Manage Agent Kit

skill-cubxxw-agent-kit-manage-agent-kit · by cubxxw

Audit, initialize, upgrade, synchronize, discover, and safely curate a shared Agent Skills repository across Claude Code, Codex, Qwen Code, OpenCode, Pi, OpenClaw, and compatible hosts. Use when setting up a machine or server, finding top GitHub skills, checking skill or upstream drift, adding or updating a skill, integrating CC Switch, resolving cross-agent installation conflicts, or reviewing w…

No reviews yet
0 installs
24 views
0.0% view→install

Install

$ agentstack add skill-cubxxw-agent-kit-manage-agent-kit

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-cubxxw-agent-kit-manage-agent-kit)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Manage Agent Kit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Manage Agent Kit

Treat the checked-out agent-kit repository as the canonical source. Agent hosts receive views of the same skill directories through symlinks.

Start with evidence

  1. Run ./bin/agent-kit doctor --strict.
  2. Run ./bin/agent-kit status --profile full-stack --tool core.
  3. Inspect catalog.json before proposing changes.
  4. Read [references/operations.md](references/operations.md) for the relevant

operation.

Do not silently replace a real directory or a symlink owned by another tool. Report the exact conflict and preserve it.

Install or repair links

Use the smallest applicable profile:

  • base: only this management skill.
  • developer: source-grounded engineering and agent infrastructure.
  • design: recursive direction branching, UI/UX evidence, and frontend

preflight.

  • full-stack: recommended personal workstation.
  • top: every broadly useful skill that passed the full adoption gate.
  • all: compatibility alias for top.

Preview first:

./bin/agent-kit install --profile full-stack --tool core --dry-run

Then install. Use --replace-managed only for stale symlinks that already point into this checkout. It must never replace copied files or foreign links.

Curate a new skill

Read the checkout’s docs/top-skills.md before broad discovery. It separates adopted, on-demand, and discovery-only sources.

Accept a skill only when all gates pass:

  1. It solves a repeated, current task with clear marginal value.
  2. It does not duplicate a host-provided or already installed capability.
  3. Its source is attributable, actively maintained, and pinned to a full

commit SHA.

  1. Its redistribution license is explicit. Do not vendor an unlicensed skill.
  2. Read every executable file and inspect network, credential, and destructive

behavior.

  1. Add it to catalog.json and the narrowest profile.
  2. Run the creator validator when first-party skill instructions change.
  3. Run the repository tests, doctor --strict, and the public safety scan.
  4. Install it into the intended hosts and verify every link resolves to the

same target.

Record rejected or deferred candidates in docs/skill-selection.md; this keeps the catalog small without losing the research.

Discover top skills

Treat rankings and awesome lists as candidate generators:

  1. Search official or product-owned repositories first.
  2. Use GitHub activity and skills.sh installs only as discovery signals.
  3. Identify the narrow skill directory that matches a repeated current need.
  4. Compare its triggers against the installed catalog.
  5. Return an adoption, on-demand, watch, or reject decision with evidence.
  6. Update docs/top-skills.md without installing anything unless the full

curation gate passes.

Never bulk-install a pack because it is popular, official, or listed in the radar.

Update a vendored skill

Run scripts/check_upstreams.py. If an update exists:

  1. Review upstream commits between the pinned and proposed SHAs.
  2. Run scripts/update_vendor.py --ref .
  3. Review the entire vendor diff, especially scripts and dependencies.
  4. Re-run all validation and security gates.

Never auto-merge upstream skill changes.

Public boundary

Never commit credentials, auth state, transcripts, memories, machine-local overrides, private Brain content, or absolute personal home paths. Public templates may name environment variables but may not contain their values.

Keep model choice, OAuth state, API tokens, and per-machine approvals local. Only portable instructions, skills, hook logic, safe templates, source pins, and license evidence belong here.

Completion criteria

Finish only when:

  • repository validation passes;
  • no public-boundary finding remains;
  • every selected skill is linked into the intended agent directories;
  • all managed links resolve to one canonical source;
  • conflicts, deferred candidates, radar status, and upstream pins are explicit.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.