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.

68

Quality

85%

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

86%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 tight, well-structured instruction-only skill that assumes Claude's competence and gives concrete formatting rules. Its main weakness is the absence of a complete worked Fountain example that would make the guidance fully copy-paste ready.

Suggestions

Add one complete worked example of a short Fountain-formatted scene (scene heading, action, character cue, dialogue, parenthetical) to lift actionability to fully executable.

Frame the skill's single action more explicitly as a procedure (e.g., "When producing Fountain output: 1) open with a scene heading…") to sharpen workflow clarity.

Clarify how the "storyboard JSON prep" heuristic connects to the core formatting rules so it reads as actionable guidance rather than an aside.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — no padding, no explaining what a screenplay or Fountain is, and every bullet states a usable rule or heuristic that earns its place.

5 / 5

Actionability

Concrete, executable formatting rules ("INT.", "EXT.", uppercase character cues, dialogue follows cues) are directly applicable, but a complete worked Fountain example is missing — a minor gap for a format-producing skill.

4 / 5

Workflow Clarity

As a simple single-purpose skill the usage is clear and unambiguous, but the single action is not crisply framed as a procedure and no output-process framing is given.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Source Basis, Rules, Writing Heuristics, Do Not) and no need for external references, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

78%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.

A well-targeted description that names a clear niche with concrete trigger terms and explicit what/when guidance. It is held back from the top level only by task-noun rather than action-verb framing and the absence of file-extension/synonym triggers.

Suggestions

Reframe capabilities with action verbs (e.g., "Format screenplays, write scenes, lay out dialogue…") to strengthen specificity.

Add the ".fountain" file extension and "screenwriting" synonym to broaden natural trigger coverage.

Make the "when" clause more user-mention explicit, e.g. "Use when the user asks to write or format a screenplay in Fountain."

DimensionReasoningScore

Specificity

Lists several specific capabilities — "screenplay, scene writing, dialogue formatting, beat outlines" — but frames them as task nouns rather than concrete action verbs and has minor coverage gaps (no import/export or .fountain file output).

4 / 5

Completeness

Explicitly provides both a "what" ("produce structured script text compatible with Fountain syntax") and a "when" ("Use for screenplay, scene writing…"), but the trigger guidance could be more explicit with user-mention phrasing.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("screenplay", "scene writing", "dialogue formatting", "beat outlines", "Fountain syntax") that users would actually say, but misses the ".fountain" file extension and the "screenwriting" synonym.

4 / 5

Distinctiveness Conflict Risk

Fountain/screenplay formatting is a clear niche with distinct, domain-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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.

Validation — 15 / 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.