@majiayu000/deploy
BDeploy Kaizen components with safety checks and validation
Install
agr install @majiayu000/deploy --target claudeWrites 2 files into .claude/skills/, pinned to git-b9fa5fa6.
- .claude/skills/deploy/SKILL.md
- .claude/skills/deploy/metadata.json
Document
name: deploy description: Deploy Kaizen components with safety checks and validation
Deploy workflow for Kaizen infrastructure. Follow this sequence:
- Pre-flight: Run
kubectl get nodes -o wideto verify cluster health - Validate manifests:
kubectl apply --dry-run=client -f <manifest> - Apply in order: base → storage → inference → monitoring → agents
- Post-deploy: Verify pods running, check logs for errors
Arguments: $ARGUMENTS
Safety rules:
- Always dry-run first
- Never delete namespaces
- Check node readiness before deploying GPU workloads
- Verify NFS mount from VAULT before storage-dependent deploys
Repository README
Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.
Claude Skill Registry (Data)
This repo contains the archived skill contents (the heavy, browsable skill files).
Canonical layout
- Category folders at repo root (e.g.
development/,documents/,data/, ...) - Each skill lives under a category:
<category>/<skill>/SKILL.md+<category>/<skill>/metadata.json - Case conflicts are resolved with
{name}-{owner}-{repo}suffixes (fallback:-{short-hash}).
Archive status
- Live badges above are sourced from
claude-skill-registry-corestats.json. - Counts in this README are intentionally dynamic, not hardcoded.
- If the badges look stale, refresh the
corebuild/index pipeline rather than editing numbers here.
Where the index + site live
- Core repo: https://github.com/majiayu000/claude-skill-registry-core
- Main repo (merged publish artifact): https://github.com/majiayu000/claude-skill-registry
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-b9fa5fa695162026-07-31