Cleanup Reporter

Low Risk

Scan your machine for large directories, duplicate files, and stale resume files.

0👍 0 upvotes0

Editorial assessment

Where Cleanup Reporter fits

Cleanup Reporter is currently positioned as a other skill for engineering teams running repository, CI, and issue workflows. Based on the available metadata, the core job to be done is straightforward: scan your machine for large directories, duplicate files, and stale resume files.

The current description adds a practical clue about how the skill behaves in the field: scan your machine for large directories, duplicate files, and stale resume files. source: https://clawhub.ai/malavyaraval/cleanup reporter version: 0.1.0. Combined with a manual install path, this makes Cleanup Reporter easier to evaluate than pages that only list a name and external link.

Cleanup Reporter can usually be trialed quickly, as long as the source and permissions still get reviewed. No explicit permission list is published in the current record, so verify the runtime surface in the source repository before rollout.

Best fit

engineering teams running repository, CI, and issue workflows

Install surface

Ask the maintainer for a verified install path before adoption.

Source signal

Public source link available

Workflow tags

No structured tags are published yet.

Adoption posture

Install command not documented

Risk review

Can usually be trialed quickly, as long as the source and permissions still get reviewed

Best-fit workflows

Cleanup Reporter is best evaluated in other environments where scan your machine for large directories, duplicate files, and stale resume files

Shortlist it when you need a public, source linked skill that can be tested from a real install command instead of a mock integration

Use a disposable workspace for the first pass so you can confirm the install flow, repository quality, and downstream permissions before broader adoption

About

Scan your machine for large directories, duplicate files, and stale resume files. Source: https://clawhub.ai/malavyaraval/cleanup-reporter Version: 0.1.0

Rollout checklist

Review the source repository at https://clawhub.ai/malavyaraval/cleanup-reporter and confirm the README, maintenance activity, and install notes are still current.

Document a reproducible install path before trying to operationalize Cleanup Reporter across multiple machines or contributors.

Capture the permissions and runtime surface during the first install, because the current record does not yet publish a detailed permission map.

Decide whether Cleanup Reporter belongs in a production workflow, an internal ops stack, or a one-off experiment before wider rollout.

FAQ

What does Cleanup Reporter help with?

Cleanup Reporter is positioned as a other skill. Based on the current summary and tags, it is most relevant for engineering teams running repository, CI, and issue workflows, especially when the workflow requires scan your machine for large directories, duplicate files, and stale resume files.

How should I evaluate Cleanup Reporter before using it in production?

Start with the source repository or original documentation, document a reproducible install path, and only move to production after you verify permissions, dependencies, and rollback steps.

Why does this page include editorial guidance instead of only the upstream docs?

ClawList is trying to make each skill page more useful than a bare directory listing. That means surfacing practical signals like the install surface, source link, permissions, workflow fit, and rollout considerations in one place.

Who is the best first user for Cleanup Reporter?

The best first evaluator is usually the operator or engineer already responsible for other workflows, because they can verify whether Cleanup Reporter matches the current stack, risk tolerance, and maintenance expectations.

View Source Code

Share

Send this page to someone who needs it

Related Skills