CtrlK
BlogDocsLog inGet started
Tessl Logo

screenplay-fountain-format

Use for screenplay, scene writing, dialogue formatting, beat outlines, and any request that should produce structured script text compatible with Fountain syntax.

74

Quality

92%

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

85%

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

A concise, well-organized instruction-only skill that states clear formatting conventions without redundant explanation. Its main weakness is the absence of a concrete worked example showing the Fountain elements assembled into actual script output, which limits actionability.

Suggestions

Add a short worked example showing a complete Fountain-formatted scene (scene heading, action, uppercase character cue, dialogue, parenthetical) so Claude has a copy-paste-ready model of the assembled output.

Tighten the subjective rules (e.g. 'Parentheticals are sparse and functional', 'Transitions are only used when they add rhythm or meaning') with a concrete heuristic or one-line example of correct vs incorrect usage.

Clarify the 'storyboard JSON prep' heuristic with a brief snippet of the expected sequence-anchor structure, since it is the only non-formatting action mentioned and is currently underspecified.

DimensionReasoningScore

Conciseness

The body is lean with no padding and does not explain concepts Claude already knows (e.g. what a screenplay or Fountain is); every section (Source Basis, Rules, Heuristics, Do Not) earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Several rules are concrete and executable ('INT.', 'EXT.', uppercase character cues, dialogue follows cues), but there is no assembled worked example of Fountain output and some rules are subjective ('sparse and functional', 'add rhythm or meaning'), fitting the 'some concrete guidance but incomplete / missing key details' anchor rather than copy-paste-ready level 3.

2 / 3

Workflow Clarity

This is a simple single-purpose skill under 50 lines with no destructive or batch operations, and the single action (apply these formatting rules when writing screenplay text) is unambiguous, so workflow clarity scores 3 per the simple-skills note.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed for a sub-50-line skill; content is organized into clearly labeled sections, satisfying the 'well-organized sections' criterion for level 3 under the simple-skills note.

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.

A strong, concise description that states both what the skill produces (Fountain-compatible structured script text) and when to use it via an explicit 'Use for' trigger clause. It occupies a clear niche and uses natural trigger terms without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — 'screenplay, scene writing, dialogue formatting, beat outlines' — plus the output form 'structured script text compatible with Fountain syntax', matching the 'lists multiple specific concrete actions' anchor rather than the domain-only level 2.

3 / 3

Completeness

The 'Use for ...' clause provides explicit trigger guidance (the 'when'), and 'produce structured script text compatible with Fountain syntax' states the 'what', so both are present and not capped at 2.

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say ('screenplay', 'scene writing', 'dialogue formatting', 'Fountain', 'script'), giving good keyword coverage; not merely technical jargon as at level 1.

3 / 3

Distinctiveness Conflict Risk

Fountain/screenplay is a clear niche with distinct triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor.

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
nolanx-ai/nolanx.ai
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.