CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seven-prompt-content-engine

Walks a user from one rough content idea to a finished post, platform-adapted variants, and repurposed follow-on assets using a 7-step sequential prompting workflow. Use when the user wants to turn a half-formed idea, frustration, story, or client situation into publishable content quickly and consistently — covering idea extraction, hook generation, outline, draft, humanizer pass, platform adaptation (LinkedIn, Reddit, X/Twitter, newsletter, Telegram), and repurpose engine.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only skill: the 7-step pipeline is unambiguous with explicit feedback loops and a pre-finalization checklist, per-step guidance is concrete enough to execute directly, and detailed prompt templates are correctly offloaded to a one-level-deep reference. The only weakness is redundancy between the Core Operating Rules and the per-step constraint blocks.

Suggestions

Trim the Core Operating Rules list to rules that are not already stated per-step (e.g., drop the Step 4/5/6 restatements about voice constraints, AI-pattern auditing, and native platform adaptation) and keep only genuinely cross-cutting rules like linearity and the revise-pause behavior.

Consolidate the Output Format section with the Quality Checklist, since both govern what the user sees at the end of a run — one 'Deliverables & final check' section would remove the duplication between 'Label all assumptions separately' handling in each.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no explanations of what platforms or writing concepts are — but the 'Core Operating Rules' section restates per-step constraints already given in Steps 1, 4, 5, 6, and 7 ('one strong angle... never return a menu', 'match only voice constraints the user explicitly provides', 'audit for detectable AI patterns', 'adapt natively per platform; do not copy-paste'). These are minor instances of over-explanation that could be trimmed, fitting the level-4 anchor rather than the 'every token earns its place' of level 5; it is clearly above the 'some unnecessary explanation' of level 3.

4 / 5

Actionability

Fully executable instruction-only guidance: exact output shapes per step (5 hooks with five named structures, outline with per-section purpose/key point/proof, 8 explicit audit categories, 8–10 standalone hooks and one-liners), concrete banned-phrase examples ('In today's post...', 'Delve into...', 'It's worth noting that...'), a labeled intake table with required/optional flags, and full prompt templates offloaded to a real reference file. Specific guidance covers the common cases, matching the level-5 anchor.

5 / 5

Workflow Clarity

Seven clearly sequenced steps where 'output of each step is the input for the next', with an explicit feedback loop ('Pause after any step if the user asks to revise'), assumption labeling when intake is incomplete, and a final Quality Checklist shown before finalizing a full run — validation checkpoints and a checklist for a complex process, matching the level-5 anchor. The operations are non-destructive, so no validation cap applies.

5 / 5

Progressive Disclosure

The body carries behavioral rules and step definitions while the bulk prompt text lives in a single clearly signaled, one-level-deep reference ('Use the templates in [./references/prompt-templates.md](./references/prompt-templates.md)') — a real file, verified present. The split is appropriate for discovery and navigation matches the level-5 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

19

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person, concrete action inventory, explicit 'Use when...' trigger clause with natural user phrasing, and platform-specific detail. Only the broad top-level framing leaves slight overlap risk with general writing assistants.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: 'idea extraction, hook generation, outline, draft, humanizer pass, platform adaptation (LinkedIn, Reddit, X/Twitter, newsletter, Telegram), and repurpose engine' — each pipeline stage is a named capability, matching the level-5 anchor rather than the 'several specific actions; minor gaps' of level 4.

5 / 5

Completeness

Explicitly answers both: what ('Walks a user from one rough content idea to a finished post, platform-adapted variants, and repurposed follow-on assets using a 7-step sequential prompting workflow') and when ('Use when the user wants to turn a half-formed idea... into publishable content quickly and consistently') with concrete trigger phrases — the exact level-5 pattern.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered: 'rough content idea', 'half-formed idea, frustration, story, or client situation', 'publishable content', plus platform names (LinkedIn, Reddit, X/Twitter, newsletter, Telegram) as synonyms users would actually say. Fits the 'comprehensive coverage of natural terms including synonyms' anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The 7-step pipeline with humanizer pass and repurpose engine is a clear niche with distinct triggers, but the broad 'turn... into publishable content' framing has minor overlap risk with generic writing/editing assistants. Fits 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict level 5, and is well above the overlap-prone level 3.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Jamie-BitFlight/claude_skills

Path

.claude/skills/seven-prompt-content-engine/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.