content-creator
Use when an org role acts as content creator and must turn one core idea into platform-native assets across formats and platforms. Covers hooks, consistent voice and per-asset KPIs; for drafting specific posts and threads use content-engine.
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- content-creator
- tags
- [ "writing", "marketing", "content", "social" ]
- tools
- []
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- description
- Use when an org role acts as content creator and must turn one core idea into platform-native assets across formats and platforms. Covers hooks, consistent voice and per-asset KPIs; for drafting specific posts and threads use content-engine.
03 SKILL.md 正文
Content Creator — Best Practices
Focus
Produces and repurposes content across formats and platforms — turning one core idea into platform-native assets that build audience and drive measurable outcomes, not just volume.
Best practices
- Define audience and goal before choosing platforms — don't try to be everywhere at once.
- Create one core asset, then adapt it per platform's native format and expectations rather than cross-posting identically.
- Prioritize short-form vertical video where discovery algorithms reward it (Reels, Shorts) without abandoning long-form where it drives deeper engagement.
- Open with a strong, specific hook in the first 1-3 seconds/lines — attention is won or lost immediately.
- Keep branding and voice consistent across formats even as the format itself varies.
- Check performance analytics regularly and let data — not intuition — decide what gets repeated or dropped.
- Favor content that reflects real experience and specificity over generic, interchangeable AI-flavored output.
Common pitfalls
- Publishing the same asset unchanged across every platform instead of adapting to format norms.
- Optimizing for vanity metrics (views, likes) instead of the underlying business goal (leads, signups, retention).
- Inconsistent posting cadence — sporadic bursts followed by silence perform worse than modest but steady output.
- Treating repurposing as an afterthought instead of planning it into the original content's structure.
Tools & techniques
- Content pillars/themes to keep output focused rather than reactive to every trend.
- A repurposing map: one long-form piece → clip/carousel/thread/short-form derivatives, each edited for its platform.
- A small, consistent set of KPIs tracked per asset (e.g. watch-through rate, saves, click-through) reviewed on a weekly cadence.
- Hook-testing: several opening variants for the same asset, measured against early retention/drop-off.
04 同仓库更多 Skills
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.