Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Write or revise filmable scenes, dialogue, beats and Fountain-style excerpts.
--- name: screenplay-and-scene-writing description: "Write and revise screenplay scenes, dialogue, beats, emotional turns, pacing, visual action, and screenplay-style excerpts from short-film concepts or outlines." --- # screenplay-and-scene-writing ## When to use - The user asks for screenplay pages, scene writing, dialogue, beats, pacing, emotional turns, or visual storytelling. - The user provides a treatment, outline, scene purpose, or character conflict and wants it dramatized. - The task is to revise a scene for clarity, subtext, tension, or cinematic action. ## When not to use - The user only needs shot list extraction from already final pages. - The user asks for image/video model parameters. - The user wants a full prose-fiction workflow rather than screenplay or scene design; route early concept work to `short-film-development`. ## Required inputs - Scene purpose - Characters present - Location and time - Before/after story state - Desired tone or genre ## Optional inputs - Dialogue constraints - Runtime/page target - Visual bible anchors - Specific format requirements, including Fountain ## Workflow 1. Define the scene transaction: who wants what, who resists, what changes. 2. List beats as playable actions, not explanations. 3. Choose the dominant point of view and what the audience knows at the start. 4. Write action lines as visible and audible behavior with concise sensory detail. 5. Write dialogue with subtext: characters pursue tactics, avoid saying the theme directly, and reveal pressure through choices. 6. If the user needs importable screenplay text, output strict Fountain markup and keep camera/production notes outside the scene. 7. Add an emotional turn and a final image or button that changes momentum. 8. Revise for compression: remove repeated beats, expository greetings, and internal states that cannot be filmed. ## Decision logic - If dialogue carries exposition, convert part of it to behavior, prop use, interruption, or silence. - If a beat cannot be shot, rewrite it as a visible action or sound. - If the scene has no reversal, add discovery, choice, escalation, or cost. - If prompts are a downstream goal, tag key visual anchors after the scene. ## Output formats - Beat sheet - Screenplay scene excerpt - Fountain scene - Dialogue pass - Visual action pass - Scene revision notes - Prompting handoff notes ## Quality checks - Every line changes tactic, pressure, or information. - Action lines are filmable and not novelistic. - Characters sound distinct by goal, rhythm, and avoidance strategy. - The scene has a clear entry state, turn, and exit state. - Important continuity details are captured for the bible. ## Anti-patterns - Explaining backstory before the conflict starts - Writing camera directions inside a draft unless requested - Dialogue that states exactly what characters feel - Unfilmable internal adjectives without behavior - Scenes that end where they began ## Exit criteria - A scene or beat sheet is ready for shot breakdown, revision, or prompt generation. ## Supporting files Read only the supporting file needed for the active task: - `references/scene_construction.md` - `references/dialogue_and_subtext.md` - `references/screenplay_format.md` - `references/fountain_workflow.md` - `templates/screenplay_scene.md` - `templates/fountain_scene.md` - `templates/beat_sheet.md`
Write or revise filmable scenes, dialogue, beats and Fountain-style excerpts.
The complete original workflow, with source attribution and the limitations below.
Confirm the task, check actual dependencies, then apply the relevant original instructions within authorized scope.
Scene purpose, characters, location/time, story-state change and tone.
Published after an obvious-danger screen under the user-requested policy, not a functional test. Supporting files required conditionally by the original are not supplied: references/scene_construction.md, references/dialogue_and_subtext.md, references/screenplay_format.md, references/fountain_workflow.md, templates/screenplay_scene.md, templates/fountain_scene.md, templates/beat_sheet.md. Related model-adaptation/continuity handoffs must be available for the actual task; loading this source does not load them. No media generation, model-capability verification or code execution was performed. Treat named-model parameters as unknown until checked and use authorized references/assets.
Use Screenplay Scene Writing for [TASK]. Ask for missing inputs: Scene purpose, characters, location/time, story-state change and tone. Check the declared dependencies and limitations before execution. Return the original output structure with known facts, assumptions and unresolved requirements separated.
Claiming that unavailable source dependencies are bundled or that generated outputs, integrations or model behavior have been tested. Actual media generation without a separately available authorized tool.
M11 added German routing, task inputs and explicit source-package limitations; the original author remains separate from M11 curation. Published after an obvious-danger screen under the user-requested policy, not a functional test. Supporting files required conditionally by the original are not supplied: references/scene_construction.md, references/dialogue_and_subtext.md, references/screenplay_format.md, references/fountain_workflow.md, templates/screenplay_scene.md, templates/fountain_scene.md, templates/beat_sheet.md. Related model-adaptation/continuity handoffs must be available for the actual task; loading this source does not load them. No media generation, model-capability verification or code execution was performed. Treat named-model parameters as unknown until checked and use authorized references/assets.
MIT License Copyright (c) 2026 0xhughs Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.