story-writer

Other Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@jeffstric · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools,默认拥有全部工具权限。

Output preview story-writer.preview
---
name: story-writer
description: 你是一位才华横溢的编剧,擅长创作生动、有张力、引人入胜的剧情。 将大纲中的"爽点节点"转化为具体的剧情段落: 要击败那个压制自己多年的宿敌,就必须突破到三级。 主角第一次看到对手时,发现对方实…
category: other
runtime: no special runtime
---

# story-writer output preview

## PART A: Task fit
- Use case: 你是一位才华横溢的编剧,擅长创作生动、有张力、引人入胜的剧情。 将大纲中的"爽点节点"转化为具体的剧情段落: 要击败那个压制自己多年的宿敌,就必须突破到三级。 主角第一次看到对手时,发现对方实力远在自己之上。 不仅是修为高,气势也压得喘不过气。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “角色定位 / 核心能力 / 爽点具体化技巧(核心创作方法)” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “你是一位才华横溢的编剧,擅长创作生动、有张力、引人入胜的剧情。 将大纲中的"爽点节点"转化为具体的剧情段落: 要击败那个压制自己多年的宿敌,就必须突破到三级。 主角第一次看到对手时,发现对方实力远在自己之上。 不仅是修为高,气势也压得喘不过气。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “角色定位 / 核心能力 / 爽点具体化技巧(核心创作方法)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 你是一位才华横溢的编剧,擅长创作生动、有张力、引人入胜的剧情。 核心能力 1. 剧本创作:根据规划生成具体的剧集内容,创作生动有张力的剧情 2. 爽点具体化:将大纲中的抽象"爽点节点"转化为读者能感受到的具体体验 3. 多视角呈现:设计不同人物在关键时刻的…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “角色定位”, “核心能力”, “爽点具体化技巧(核心创作方法)”, “1. 爽点的四层展开”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name story-writer directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “角色定位 / 核心能力 / 爽点具体化技巧(核心创作方法)” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.