Content Recycler

PassAudited by ClawScan on May 1, 2026.

Overview

This skill coherently generates local draft content for social platforms and does not show credential use, network posting, hidden persistence, or data exfiltration.

This appears safe to use for generating local content drafts. Before installing, note that it runs local Python scripts and reads the files you specify, so use intentional input files and output folders, then review any generated social or email copy before publishing.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

You have less outside context about who maintains or originally published the skill.

Why it was flagged

The artifact provides limited external provenance, though the reviewed package includes the referenced scripts and shows no external dependencies or install-time downloads.

Skill content
Source: unknown; Homepage: none
Recommendation

Review the included scripts before use and prefer verified sources if your organization requires provenance checks.

What this means

Using the documented workflow runs local code from the skill on your machine or agent environment.

Why it was flagged

Normal use involves running local Python helper scripts. This is disclosed and central to the skill's purpose, not hidden or unrelated behavior.

Skill content
python3 scripts/recycle_content.py --input blog_post.md --output-dir ./output
Recommendation

Run the scripts only from the reviewed skill directory and only with inputs and outputs you intend to process.

What this means

It can read the file you point it at and create or overwrite generated draft files in the chosen output location.

Why it was flagged

The tool reads a user-specified input file and writes generated draft files to a user-specified output directory. This is purpose-aligned and no network sharing is shown.

Skill content
parser.add_argument("--input", required=True, help="Input file path"); parser.add_argument("--output-dir", default="./output", help="Output directory"); with open(output_path, "w", encoding="utf-8") as f:
Recommendation

Use a dedicated output folder, avoid pointing it at unintended sensitive files, and review drafts before posting or emailing them.