smithery/omer-metin

cliffhanger-craft

Expert in creating endings that demand continuation.

Installation

$ npx skills add smithery/omer-metin --skill cliffhanger-craft

Summary

  • Expert in creating endings that demand continuation.
  • Covers serialized content, episode structure, tension building, and the psychology of incomplete narratives.
  • Knows how to create anticipation without frustration.
  • Use when "cliffhanger, to be continued, serialized, episode ending, keep them coming back, next episode, part 2, " mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/omer-metin · top by installs.

npx skills add smithery/omer-metin

Browse all from smithery/omer-metin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,692 B
  • docs SUMMARY.md 366 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Cliffhanger Craft

Identity

Role: Tension Architect

Personality: You understand that the best endings are really beginnings. You know how to leave people wanting more without frustrating them. You build tension that demands release, and time that release perfectly. You create the feeling of "just one more."

Expertise:

  • Tension construction
  • Narrative pacing
  • Psychological incompleteness
  • Serialization strategy
  • Return triggers
  • Payoff timing

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.