spinosa-janitor

Audits workspace hygiene, detects stale files and broken wikilinks, and proposes archival moves to .trash/.

7|Updated May 13, 2026
One-click install
npx skills add https://github.com/medialab/spinosa --skill spinosa-janitor-medialab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spinosa-janitor
Source: https://github.com/medialab/spinosa/tree/main/workspace-template/.opencode/skills/spinosa-janitor
Command: npx skills add https://github.com/medialab/spinosa --skill spinosa-janitor-medialab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research workspaces accumulate stale files, broken wikilinks, orphaned documents, and outdated reports over time, making it hard to trust and navigate the collection. This Skill audits the workspace for hygiene issues and proposes safe archival moves without ever deleting anything. ## Core Features & Use Cases - Hygiene Auditing: Checks raw copies against their sources, validates wikilinks, detects orphaned files, and flags stale entries based on configurable age thresholds. - Safe Archival: Never deletes files — moves them to .trash/ only after explicit user confirmation, with every proposed move documented and reasoned. - Hygiene Score Dashboard: Generates a Unicode gauge report showing overall workspace health, files checked, issues found, and proposed moves. - Use Case: After months of research, run a hygiene audit to find broken wikilinks, raw copies whose sources no longer exist, and reports older than 90 days, then confirm which ones to archive. ## Quick Start Ask the agent to audit the workspace for stale files and broken links and write a hygiene report before proposing any cleanup moves.

Frequently Asked Questions about spinosa-janitor

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

FAQPage Schema
How do I audit a research workspace for stale files?▼

Run the janitor workflow, which compares each file's updated date in YAML frontmatter against the stale_after_days threshold from the workspace configuration. It writes a hygiene audit report listing stale files, broken links, and orphaned documents before any action is taken.

How to find broken wikilinks in a markdown workspace?▼

The audit greps all files for [[ wikilink patterns and checks whether each linked target file exists on disk. Missing targets are flagged as broken_link issues in the cleanup report.

Does the cleanup agent delete files permanently?▼

No, files are never deleted. Confirmed items are moved to a .trash/ directory, and every proposed move requires explicit user confirmation with a documented reason before execution.

Can I configure how old a file must be before it is flagged as stale?▼

Yes, staleness thresholds are read from the workspace configuration file via the stale_after_days setting. The default is 30 days for temporary files and 90 days for reports.

What happens to files still referenced by active maps or reports?▼

Files referenced by active maps or reports are protected and will not be moved. The audit only proposes archival for orphaned or stale files with no active references.