CtrlK
BlogDocsLog inGet started
Tessl Logo

long-form-content-frameworks

Patterns for individual long-form content pieces. Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials. The structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat. Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces. Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes. Also triggers when a piece is over 3,000 words and the team is unsure how to structure it, when a long-form draft feels padded or saggy, or when a flagship asset needs the depth to actually earn the length.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a well-structured editorial playbook with strong actionability, a clear sequenced framework with audit checkpoints, and exemplary progressive disclosure via one-level-deep references that all resolve to real files. Its only real weakness is conciseness: the core failure-mode framing and the 12-consideration framework recap material already covered in earlier sections.

Suggestions

Consolidate the repeated bloggy-long/academic-bloat framing: define it once in its dedicated section and reference it from the intro, failure modes, and closing rather than restating each time.

Trim the '12 considerations' section to either new synthesis or cross-references to the detailed sections, since it currently restates the lede, section-weight, citation, visual, and closing guidance already covered above.

Consider moving the rapid-fire 'Common failure modes' list (which overlaps the closing-patterns and lede-patterns sections) entirely into common-long-form-failures.md and keeping only a brief pointer in the body.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes editorial competence, but the bloggy-long/academic-bloat framing is restated in the intro, its own section, the failure modes, and the closing, and the '12 considerations' section largely recapitulates the preceding sections. It is not at 3 because some material could be tightened without loss; it is not at 1 because it does not explain basic concepts Claude already knows and most tokens carry load.

2 / 3

Actionability

As an instruction-only skill it provides concrete, specific guidance: named lede and closing patterns, exact section-weight percentages (e.g. 'Body 60-70%'), and explicit audit tests ('If one section is more than 3x the length of another bearing similar argumentative load...'). The rubric does not penalize absence of code when guidance is this actionable, so it reaches 3; it is not at 2 because the guidance is copy-ready and specific rather than abstract.

3 / 3

Workflow Clarity

The '12 considerations for long-form content' provides a clearly sequenced planning/auditing workflow, and audits like the 3x section-weight test and the litmus test ('would cutting this section weaken the argument') act as explicit checkpoints. It is not at 2 because the sequence and checkpoints are explicit; it is not a destructive/batch operation, so missing validation feedback loops do not cap it.

3 / 3

Progressive Disclosure

Each major section closes with a one-level-deep, clearly signaled reference ('Detail in [`references/...`]'), all nine referenced files exist in the bundle, and a 'Reference files' index lists them with descriptions. It is not at 2 because the split is clean and navigation is easy rather than ad-hoc.

3 / 3

Total

11

/

12

Passed

Description

100%

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

The description is strong across all dimensions: it names concrete formats, provides explicit and broad trigger terms, answers both what and when, and clearly distinguishes itself from the sibling pillar-content-architecture skill. Third-person voice is used throughout, consistent with the rubric guidelines.

DimensionReasoningScore

Specificity

Lists multiple concrete long-form formats ('Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials') and a specific distinguishing function ('structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat'). It names the domain and its concrete sub-types rather than vague actions, matching the score-3 anchor; it is not at 2 because coverage is comprehensive, not partial.

3 / 3

Completeness

It answers both 'what' (patterns/structural disciplines for individual long-form pieces and their formats) and 'when' via explicit 'Triggers on...' and 'Also triggers when...' clauses. It is not at 2 because the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

The explicit 'Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes' plus 'Also triggers when a piece is over 3,000 words...' gives broad coverage of natural terms a user would say. It is not at 2 because it covers many common variations rather than only a few.

3 / 3

Distinctiveness Conflict Risk

It explicitly carves a niche ('Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces'), giving a clear piece-scope vs hub-scope distinction unlikely to trigger the wrong skill. It is not at 2 because the boundary is stated explicitly rather than merely implied.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.