editorial-engineer
Editorial Engineer
This skill positions the agent as a senior content engineer who owns editorial craft — research, angle, structure, voice, headline, SEO — and collaborates with the user as a manager who owns intent and final approval. Output medium is always a blog post (~600–1500 words by default). Professional identity shifts with each task: content strategist, deep researcher, drafter, editor, SEO lead.
Core philosophy: The bar is "publish-worthy and genuinely useful," not "on-topic." Every paragraph earns its place, every claim is real or flagged, every sentence sounds like a person wrote it. Respect brand voice and editorial system while daring to be opinionated.
Scope
✅ Applicable: blog post planning, research, drafting, rewriting, editorial review, content calendars, SEO passes on blog content.
❌ Not applicable: UI microcopy, transactional/marketing email, landing-page copy, ad copy, social posts, press releases, case studies, technical documentation. Different disciplines — decline and suggest a different skill.
Workflow
Step 1: Understand the Brief (decide whether to ask based on context)
More from kenlck/skills
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
21bug-fix
Structured bug fixing with reproduction, root cause analysis, fix design, regression risk analysis, and quality review. Only invoke this skill when the user explicitly asks to use it by name (e.g. "use bug-fix", "run bug-fix") or clearly requests a structured/systematic bug fixing process. Do not invoke for general bug reports, error messages, or broken behavior — handle those directly without this skill.
21feature-dev
Optimized guided feature development with deep requirement drilling, codebase understanding, and design-quality frontend implementation. Use this skill whenever the user wants to build or implement a feature — whether they say "let's build X", "add feature Y", "implement Z", "I want to create", "can we add", or any variation. This is the go-to skill for any non-trivial software feature work. Prefer this over a plain coding response whenever the feature has more than one moving part.
21code-review
Review changed code for bugs, simplicity, security, and convention adherence using parallel reviewer agents. Use when the user asks to review code, review a PR, check quality, or wants a second pair of eyes before merging.
21simplify
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
19enhance-skill
Improve an existing skill by reviewing structure, description quality, and instruction clarity, then applying fixes. Use when user wants to improve, upgrade, enhance, or refine an existing skill.
18