Initial commit: opencode config with 32 skills, 3 agents, 11 MCPs

- Cross-platform install scripts (Windows PowerShell + Unix bash)
- Template-based config generation with env var support
- Skills: coding-standards, frontend-patterns, backend-patterns,
  security-review, tdd-workflow, e2e-testing, deep-research,
  exa-search, content-engine, crosspost, x-api, and 20 more
- Agents: explorer, reviewer, docs-researcher
- MCPs: codegraph, brave-search, playwright, github, context7,
  exa, memory, sequential-thinking, git, filesystem

skills/article-writing/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: article-writing
+description: Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
+---
+
+# Article Writing
+
+Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.
+
+## When to Activate
+
+- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
+- turning notes, transcripts, or research into polished articles
+- matching an existing founder, operator, or brand voice from examples
+- tightening structure, pacing, and evidence in already-written long-form copy
+
+## Core Rules
+
+1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
+2. Explain after the example, not before.
+3. Keep sentences tight unless the source voice is intentionally expansive.
+4. Use proof instead of adjectives.
+5. Never invent facts, credibility, or customer evidence.
+
+## Voice Handling
+
+If the user wants a specific voice, run `brand-voice` first and reuse its `VOICE PROFILE`.
+Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.
+
+If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
+
+## Banned Patterns
+
+Delete and rewrite any of these:
+- "In today's rapidly evolving landscape"
+- "game-changer", "cutting-edge", "revolutionary"
+- "here's why this matters" as a standalone bridge
+- fake vulnerability arcs
+- a closing question added only to juice engagement
+- biography padding that does not move the argument
+- generic AI throat-clearing that delays the point
+
+## Writing Process
+
+1. Clarify the audience and purpose.
+2. Build a hard outline with one job per section.
+3. Start sections with proof, artifact, conflict, or example.
+4. Expand only where the next sentence earns space.
+5. Cut anything that sounds templated, overexplained, or self-congratulatory.
+
+## Structure Guidance
+
+### Technical Guides
+
+- open with what the reader gets
+- use code, commands, screenshots, or concrete output in major sections
+- end with actionable takeaways, not a soft recap
+
+### Essays / Opinion
+
+- start with tension, contradiction, or a specific observation
+- keep one argument thread per section
+- make opinions answer to evidence
+
+### Newsletters
+
+- keep the first screen doing real work
+- do not front-load diary filler
+- use section labels only when they improve scanability
+
+## Quality Gate
+
+Before delivering:
+- factual claims are backed by provided sources
+- generic AI transitions are gone
+- the voice matches the supplied examples or the agreed `VOICE PROFILE`
+- every section adds something new
+- formatting matches the intended medium

skills/article-writing/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Article Writing"
+  short_description: "Long-form content in a supplied voice"
+  brand_color: "#B45309"
+  default_prompt: "Use $article-writing to draft polished long-form content in the supplied voice."
+policy:
+  allow_implicit_invocation: true