Comment To Content Recycler

Transform comments, DMs, and FAQ threads into prioritized content ideas and script-ready angles. Use when the user wants audience-driven topics, needs repeat...

Security Scan

The skill's instructions for turning comments/DMs into content are coherent, but there are a few mismatches and ambiguities (notably an external 'Creatop' handoff and vague data-collection steps) that should be clarified before installing or running it on real user data.

Purpose & Capability

The name and description (turn audience comments/DMs/FAQ into prioritized content) match the SKILL.md instructions. However the SKILL.md references a 'Creatop handoff' (sending high-priority clusters into a Creatop script queue) while the skill declares no required credentials, endpoints, or integration details for Creatop — an external integration is implied but not supported in the manifest.

Instruction Scope

Runtime instructions ask the agent to 'Collect recent comments/DM/FAQ items (e.g., 7–30 days)' but provide no guidance on source, access method, or required credentials. That ambiguity could lead an agent to expect access to private DMs or platform APIs without declared authorizations. The rest of the workflow (normalize, cluster, prioritize, generate outputs, suggest replies) stays within the stated purpose.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so there is nothing written to disk or downloaded during install. That is the lowest-risk install model and aligns with the manifest.

Credentials

The manifest declares no required environment variables or credentials, yet the README mentions handing results off to an external service ('Creatop') and processing DMs/comments (which may require platform API keys). The lack of declared credentials is a proportionality mismatch. Also, instructions emphasize preserving audience language — which could include PII or sensitive info — but provide no guidance or safeguards for handling such data.

Persistence & Privilege

The skill does not request persistent presence (always: false) and has no install scripts. It does not attempt to modify other skills or system-wide configs. Autonomous invocation is allowed by default but is not combined with other high-risk indicators here.

What to consider before installing

This skill appears to do what it says: cluster and prioritize audience comments into content ideas. Before installing or running it on real data, confirm two things with the skill author: (1) how the 'Creatop handoff' works and whether any API keys or endpoints are needed (the manifest lists none), and (2) how it expects you to provide comments/DMs (manual paste vs. platform integration). Be cautious about feeding private DMs or comments containing personal data — ask for details on privacy handling and whether the skill will transmit data to third parties. Also note the license: CC BY‑NC‑SA for non-commercial use only, so commercial use may require a paid license from Razestar.

Skill Card

• Category: Market Intelligence
• Core problem: How to convert comments/DMs into content pipeline?
• Best for: Always-on content ideation
• Expected input: Comments, DMs, objections, FAQ snippets
• Expected output: Intent clusters + prioritized content backlog
• Creatop handoff: Send high-priority clusters into Creatop script queue

What this does

Convert audience questions into ranked, script-ready content topics.

Workflow

1) Ingest and clean input

Collect recent comments/DM/FAQ items (e.g., 7–30 days).

Normalize by:

• removing duplicates
• merging near-identical phrasing
• preserving representative audience wording

2) Cluster by intent

Group into:

• how-to
• comparison
• troubleshooting
• buying concerns
• objections/myths

3) Prioritize clusters

Score each cluster:

• frequency
• urgency
• monetization relevance
• ease of production

Rank clusters before writing outputs.

4) Generate content outputs

For top clusters, provide:

• topic/title
• 3 hook options
• short script angle
• CTA tied to audience language

5) Close the loop

Add:

• which comments to reply first
• one follow-up question to collect better demand signals

Quality rules

• Keep audience language intact where useful.
• Avoid generic ideas disconnected from real comments.
• Prioritize repeated pains with commercial relevance.

License

Copyright (c) 2026 Razestar.

This skill is provided under CC BY-NC-SA 4.0 for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license.

Commercial use requires a separate paid commercial license from Razestar. No trademark rights are granted.