Loading...
Loading...
Found 8 Skills
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".
Make surgical edits to specific sections while maintaining voice cohesion across the essay
Content generation skill for the Orbitant engineering blog. Activates when creating a blog post from raw input (transcript, notes, or draft). Produces a structured, SEO-optimised article in Spanish that matches Orbitant's tone, editorial standards, and content cluster strategy. Use this skill whenever someone provides raw material and asks to turn it into a publishable blog post for the Orbitant blog.
Edit prose into a clear, specific, source-grounded version that preserves the author's meaning and voice. Use for humanizing stiff writing, removing generic phrasing, matching a supplied voice sample, diagnosing robotic prose, or drafting from the user's notes. Do not optimize for AI-detector scores or claim to prove authorship.
Capture a confirmed writing preference, editorial lesson, recurring failure pattern, or workflow improvement in the right durable context file. Use when the user asks to save, remember, codify, or turn a repeated correction into a rule.
Hussain Abbas (hussainweb) style guide — a conversational, empathetic, structured voice that writes as a senior engineer talking to a peer. ALWAYS use this skill to draft or edit a blog post, guide, TIL, reflection, round-up, or technical review in the user's own voice. Triggers on "write a blog post", "draft a TIL", "write this up", "edit my post", "in my voice", or any long-form writing meant to be published under the user's name.
Check documentation for Elastic style guide compliance using Vale linter output and style rules. Use when the user asks to check, lint, or review docs for voice, tone, grammar, formatting, accessibility, or word choice issues, or when a docs review runs. Do not trigger on ordinary drafting or editing.
General guidelines for Chinese technical writing: titles, prose, expressions to avoid, structure, and tone. Applies to all reader-facing Chinese content, including blog posts, short essays, notes, technical documentation, changelogs, and similar texts. Use when the user asks to write, revise, or polish Chinese content; writing-oriented skills such as my-blog-build also reference these guidelines.