cleanup-temp-skills

Delete STM-scoped temp-skills directories and decode-temp-* symlinks, emitting cleanup-report.yaml.

3|Updated Jan 25, 2026

Search Tags:#cleanup #symlinks #STM #filesystem safety #deterministic builds #ephemeral artifacts #decode workflow

Ready to run

npx skills add https://github.com/kapilvirenahuja/garura --skill cleanup-temp-skills

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup-temp-skills
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/cleanup-temp-skills
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill cleanup-temp-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes temporary, run-scoped “tech skills” generated during a /decode session so they do not persist beyond the intended enterprise workflow boundary.

Core Features & Use Cases

Strictly scoped cleanup: Deletes only the STM-scoped temp-skills directory and only the decode-temp-* symlinks/copies used for Skill discovery.
Path safety guards: Refuses to delete anything outside the expected STM boundary or outside the allowed Claude skills link roots.
Controlled triggering: Runs at the /decode evidence-close Phase 2 final tether (with optional force cleanup semantics).
Cleanup report output: Writes a structured cleanup-report.yaml including what was removed and what remained on partial failures.

Quick Start

Invoke cleanup at the end of your /decode run so the STM temp-skills and any decode-temp-* discovery artifacts are removed and recorded in cleanup-report.yaml.

Frequently Asked Questions about cleanup-temp-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I remove temporary symlinks and artifacts safely after a decode workflow run?▼

To remove temporary symlinks and artifacts safely after a decode workflow run, delete the STM-scoped temp-skills directory and decode-temp-* symlinks using path-boundary validation and safe unlink operations without following symlinks.

What is the safest way to clean up ephemeral build artifacts without deleting files outside the intended directory?▼

Safe ephemeral artifact cleanup requires absolute path-boundary validation that refuses to delete anything outside the expected STM boundary or allowed skills link roots, ensuring only in-scope targets are unlinked.

How do I generate a cleanup report for temporary files that partially failed to delete?▼

Generating a cleanup report for temporary files involves writing a structured cleanup-report.yaml that records successfully removed targets alongside partial_cleanup failure details for any items that remained.

When should I force trigger a cleanup for run artifacts instead of using the normal tether-triggered process?▼

Force-triggered cleanup for run artifacts should be used when you need to manually purge ephemeral skills outside the standard /decode evidence-close Phase 2 tether, whereas normal cleanup runs automatically at that checkpoint.

Does cleanup of STM-scoped temp skills support force deletion of discovery symlinks?▼

Yes, cleanup of STM-scoped temp skills supports both tether-triggered normal cleanup and force-triggered user cleanup for deleting decode-temp-* discovery symlinks or copies while applying strict filesystem safety guards.