Diagnose Content Before You Publish It

Where this fits

You have a topic approved, a draft written, and a sinking feeling the copy reads like every other AI-generated post. You paste it into your agent and get a diagnosis — not a rewrite. The dbs-content skill turns your agent into a content strategist that evaluates direction, form, and expression before you publish. It's for developers who ship content as part of their product loop and want an editorial filter, not a ghostwriter.

Why agents benefit

• Diagnoses, never generates. The agent refuses to write content for you. It evaluates whether your topic, form, and copy are correct — exactly what an agent should do when you already have the material.
• Enforces a product-first gate. Before diagnosing, it asks: do you have a product with a working payment link? No product, no content strategy. This prevents the agent from optimizing content with no conversion path.
• Breaks the death spiral. It actively pushes back on "publish more to get more traffic" thinking, redirecting you to higher-effort, higher-quality pieces instead of volume.
• Catches AI-flavored writing. It checks for telltale patterns that get content throttled, then tells you what to fix — without rewriting it for you.
• Matches form to topic. It decides whether your topic belongs in 图文, short video, long video, live stream, or article before you invest production time.

Practical scenarios

Diagnosing a draft before publishing

You run a technical newsletter. You've written a 1,200-word post about a new API. You paste it into the agent with /dbs-content and it flags the opening paragraph as generic AI filler, suggests a sharper hook, and notes the middle section lacks a concrete example. You fix it yourself — but now you know what to fix.

Form mismatch for a new topic

You have a topic — "how we migrated our database" — but you're unsure whether it works as a 5-minute video or a written walkthrough. The agent walks you through form matching, considering your audience and the topic's complexity, and recommends a written format with a short video teaser.

No topic, no product

You tell the agent you want to start a content channel. It asks what you're selling. You don't have a payment link. It stops and helps you clarify the product first — before any content planning happens.

Add it to your agent workflow

Install with:

npx skills add Pluviobyte/rnskill --skill dbs-content

Then invoke it in your agent:

/dbs-content
> Topic: "Why we chose Postgres over DynamoDB"
> Format: short video (60s)

The agent responds with a diagnosis: whether the topic is too broad for 60 seconds, what to cut, what to lead with, and whether the hook will hold attention.

Compare before adopting

Before you adopt, compare against: (1) quality signals — check the repo's commit history and issue responses; 1,381 stars is solid but verify it's actively maintained; (2) alternatives — a generic prompt like "review my copy" won't enforce the product-first gate or form-matching logic; (3) workflow fit — this skill assumes you already have a topic, so it won't help with ideation; (4) philosophy — the framework is opinionated, so if you disagree with its core principles, the diagnostic lens won't match your voice.

Why it is worth tracking

The skill has 1,381 stars and a clear, opinionated philosophy — rare in a space full of generic content prompts. It's worth tracking because it represents a shift from "AI writes for you" to "AI tells you what's wrong," a more durable workflow pattern. Evaluate it when you have a regular content pipeline and want an editorial layer that doesn't replace your voice. You can also find it in the OpenAgentSkill directory at https://www.openagentskill.com/skills/pluviobyte-dbs-content for comparison against similar skills.