Screenplay Scene Craft
Scene-level screenwriting craft: conflict ladders, dialogue mechanics, and scene diagnostics
- What
- Scene-level screenwriting craft: conflict ladders, dialogue mechanics, and scene diagnostics
- Cost
- Free
- Needs
- none — no account, no API keys.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a detailed screenplay scene-craft method: building conflict ladders, engineering dialogue mechanics, and running scene diagnostics to find what isn't working. Discovered via skills.sh, listed here with credit to its creator by @jtydhr88. Honest caveats: companion reference files carry much of the method — fetch the whole repo; works at scene level, pair with the story-structure sibling skill for the big picture. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Install
Prerequisites: none — no account, no API keys. Install "Screenplay Scene Craft" for me. A detailed scene-craft method for screenplays: conflict ladders, dialogue mechanics, and scene diagnostics. Repository: https://github.com/jtydhr88/screenwriting-skills 1. Fetch the SKILL.md file for the sw-scene-craft skill (and ALL its companion reference files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "sw-scene-craft". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. paste a scene and ask for a conflict-ladder pass or a diagnostic). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.