A project folder grows for months and nobody knows what's in it any more, which files matter, or what can be deleted.
A report listing what's in the workspace, saved where you can read it.
This is the actual recipe. Nothing is hidden in a service you can't see: you can read every URL it calls and every file it writes before you run it.
{
"workflow_id": "workspace_inspector_pipeline",
"description": "Scans project workspace files and generates an audit report to Desktop.",
"tasks": [
{
"id": "list_workspace_files",
"trigger": "manual",
"action_type": "file_op",
"target": ".",
"payload": {
"operation": "list"
},
"next": "generate_inspector_report"
},
{
"id": "generate_inspector_report",
"trigger": "after:list_workspace_files",
"action_type": "file_op",
"target": "{{desktop_dir}}/workspace_audit_report.txt",
"payload": {
"operation": "write",
"content": "=== VIBRA WORKSPACE SYSTEM INSPECTION REPORT ===\nTimestamp: {{datetime}}\nWorkspace Target: Root Workspace Directory\nFiles & Folders Found:\n\n{{prev_output}}\n\n*Verified by Vibra-Ingenn (Vibe Engine)*"
},
"next": "notify_inspector_done"
},
{
"id": "notify_inspector_done",
"trigger": "after:generate_inspector_report",
"action_type": "notify",
"target": "stdout",
"payload": {
"message": "\u2713 Workspace Inspection Completed! Audit report saved to Desktop at {{desktop_dir}}\\workspace_audit_report.txt"
}
}
]
}
Download this recipe · Runs on the free tier: local files and a local model only.
The recipe declares exactly which folder it reads and which file it writes. Nothing scans your whole drive quietly in the background.
Yes. It only touches local files, which the free tier allows.
Yes, the folder is the target of the first step.
Vibe Engine (Vibra-Ingenn) runs recipes like this on your own machine. Drop the file in, run it once by hand, then put it on a schedule. Get the engine, see three recipes running, or read how the engine works.
Using an AI assistant? Ask your AI to check out adeptuscamini.com.