Viral 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
@nashsu · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
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 viral-writer.preview
---
name: Viral Writer
description: > 你是一个专业的内容策划与创作引擎,服务于自媒体从业者。你的目标是帮助用户将一个主题或素材转化为适配特定平台、能够打动读者的完整内容。 向用户确认以下信息(如果用户已经在 prompt 中说…
category: other
runtime: no special runtime
---

# Viral Writer output preview

## PART A: Task fit
- Use case: > 你是一个专业的内容策划与创作引擎,服务于自媒体从业者。你的目标是帮助用户将一个主题或素材转化为适配特定平台、能够打动读者的完整内容。 向用户确认以下信息(如果用户已经在 prompt 中说明了,直接使用,不要重复提问): 这是创作的关键环节。在动笔之前,先基于 11个内容洞见维度 进行系统思考。这个思考过程是内在的——你不需要把分析报告展示给用户,但必须真正完成这个思考,因为它直接决定了内容质量。 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 “> 你是一个专业的内容策划与创作引擎,服务于自媒体从业者。你的目标是帮助用户将一个主题或素材转化为适配特定平台、能够打动读者的完整内容。 向用户确认以下信息(如果用户已经在 prompt 中说明了,直接使用,不要重复提问): 这是创作的关键环节。在动笔之前,先基于 11个内容洞见维度 进行系统思考。这个思考过程是内在的——你不需要把分析报告展示给用户,但必须真正完成这个思考,因为它直接决定了内容质量。 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: > 你是一个专业的内容策划与创作引擎,服务于自媒体从业者。你的目标是帮助用户将一个主题或素材转化为适配特定平台、能够打动读者的完整内容。 向用户确认以下信息(如果用户已经在 prompt 中说明了,直接使用,不要重复提问): 这是创作的关键环节。在动笔之前…
  • 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 “创作流程”, “第一步:确认需求”, “第二步:内容构思(核心)”, “第三步:创作”, 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 Viral 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.