skills/hq-content-enforcer/SKILL.md
Use when creating, writing, rewriting, editing, reviewing, or optimizing ANY content that will be seen by clients, prospects, or the public in the HQ workspace. Includes landing pages, website copy, forms, emails, proposals, case studies, social posts, presentations, blog posts, ad copy, sales scripts, and any AI-generated text for external use. MUST be invoked BEFORE writing any content. NEVER use for internal documentation, technical specs, or code comments (no brand enforcement needed). NEVER use for content strategy planning without actual content production (use content-strategist agent).
npx skillsauth add sharkitect-solutions/sharkitect-claude-toolkit hq-content-enforcerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| File | Load When | Do NOT Load |
|------|-----------|-------------|
| references/brand-quick-ref.md | Every content task (voice attributes, banned terms, tone targets) | Never skip -- this IS the brand standard |
| references/content-routing-guide.md | Every content task (maps content type to required skills and docs) | Never skip -- this IS the routing logic |
| <workforce-hq-cwd>/knowledge-base/governance/voice-profile-chris.md | Content authored AS CHRIS (from solutions@ to clients): cold-email, email-sequence, copywriting from-Chris, proposal/SOW signed by Chris, sales script | Generic Sharkitect copy not bylined as Chris (landing pages, marketing site, social posts), client's voice work, internal docs |
| IN SCOPE | OUT OF SCOPE | Use Instead |
|----------|-------------|-------------|
| Orchestrating skill invocation for content tasks | Actually writing the content | The routed skills handle writing |
| Loading brand voice requirements before writing | Brand compliance scoring after writing | hq-brand-review skill |
| Routing to correct CRO/SEO/copywriting skills | General copywriting without HQ brand context | copywriting skill directly |
| Enforcing pre-production checklist | Content strategy and editorial planning | content-strategist agent |
| Ensuring brand review runs before completion | Visual design or UI feedback | ui-ux-designer agent |
Sequence: Load brand voice -> Classify content type -> Route to skills (see references/content-routing-guide.md) -> Create checklist -> Write with skills -> Brand review -> Revise if <25 -> Present
digraph content_enforcement {
rankdir=TB;
"Content task" [shape=doublecircle];
"Client-facing?" [shape=diamond];
"Skip" [shape=box, style=filled, fillcolor="#e8e8e8"];
"Load brand + Classify + Route" [shape=box];
"Write with routed skills" [shape=box];
"hq-brand-review" [shape=box];
"Score >= 25?" [shape=diamond];
"Present" [shape=doublecircle];
"Revise" [shape=box];
"Content task" -> "Client-facing?";
"Client-facing?" -> "Skip" [label="NO"];
"Client-facing?" -> "Load brand + Classify + Route" [label="YES"];
"Load brand + Classify + Route" -> "Write with routed skills";
"Write with routed skills" -> "hq-brand-review";
"hq-brand-review" -> "Score >= 25?";
"Score >= 25?" -> "Present" [label="YES"];
"Score >= 25?" -> "Revise" [label="NO"];
"Revise" -> "hq-brand-review";
}
The full routing decision tree with all skill combinations lives in references/content-routing-guide.md. Load it every time -- it's the authoritative source for which skills to invoke per content type.
Quick reference (for classification only -- use the companion for exact skill stacks):
| Content Type | Identification Signals |
|---|---|
| K1 SoT prose | Path matches knowledge-base/governance/**/*.md or knowledge-base/strategy/**/*.md; document classified K1 in DOCUMENT-MAP; foundational SoT type (brand-identity-guide, positioning, ICP, messaging-framework, voice-profile, audience-profile). REQUIRES writing-clearly-and-concisely BEFORE drafting (preventive prose quality), not just brand-review (detective). |
| Landing page / website copy | URL destination, hero section, CTA, conversion goal |
| Email (cold/outreach) | First contact, prospecting, no prior relationship |
| Email (nurture/sequence) | Multi-touch, drip, follow-up, existing lead |
| Form / signup flow | Input fields, registration, lead capture |
| Proposal / SOW | Client deliverable, pricing, scope, timeline |
| Social post | Platform-native (LinkedIn, X, Instagram) |
| Blog / article | Educational, SEO-targeted, thought leadership |
| Presentation | Slides, pitch deck, keynote |
| Ad copy | Paid media, Google Ads, social ads |
| Case study | Client success story, results showcase |
| Sales script | Call script, demo script, objection handling |
If ambiguous: default to copywriting + hq-brand-review as minimum. Add CRO/SEO skills if there is ANY conversion or search intent.
The routing table isn't arbitrary. Each pairing exists because different content types operate on different psychological and conversion mechanisms:
Landing pages require page-cro + seo-optimizer: A landing page has two masters -- search engines (discovery) and human visitors (conversion). SEO gets the page found; CRO converts the visitor. Using copywriting alone produces persuasive text that nobody finds, or found text that nobody acts on. The skills must stack because optimizing for one without the other produces a page that fails at half its job.
Cold emails require cold-email + outreach-specialist, NOT copywriting: Cold email and marketing copy are fundamentally different disciplines. Marketing copy assumes the reader chose to be there. Cold email must earn attention from someone who didn't ask to hear from you. copywriting optimizes for persuasion; cold-email optimizes for reply rate. The deliverability rules alone (avoiding spam triggers, domain reputation, send volume) are a separate domain that copywriting doesn't cover.
Proposals require writing-clearly-and-concisely, NOT just copywriting: Proposals are evaluated by decision-makers scanning for risk signals. Persuasive writing in a proposal triggers skepticism -- it reads like a sales pitch when the reader wants evidence. writing-clearly-and-concisely produces the precision and structure that builds trust at the decision stage. Combined with copywriting for the executive summary and value framing, the two skills cover both the emotional and analytical evaluation paths.
Ad copy requires marketing-psychology: Ads operate in 3-7 seconds of attention. Standard copywriting produces clear, brand-consistent text. But ads need specific psychological triggers -- loss aversion for retargeting, social proof for cold audiences, anchoring for pricing ads. These are distinct from general persuasion and have measurable impact on CTR and conversion rate.
Forms require form-cro + signup-flow-cro: Every form field is a friction point with measurable abandonment rates. A 5-field form converts ~20% better than a 7-field form (Formstack research). The CRO skills encode field-ordering psychology, progressive disclosure patterns, and micro-copy optimization that copywriting doesn't address because form UX is a conversion engineering discipline, not a writing discipline.
User: "Rewrite the hero section on our landing page"
1. INVOKE hq-content-enforcer (this skill)
2. LOAD brand-quick-ref.md -> voice: Confident 7-9, Direct 7-9, Action-Oriented 7-9
3. CLASSIFY: Landing page (URL destination, hero section, CTA)
4. LOAD content-routing-guide.md -> Required: copywriting + page-cro + seo-optimizer + hq-brand-review
5. INVOKE page-cro -> hero needs single clear CTA above fold, benefit-first headline
6. INVOKE seo-optimizer -> primary keyword in H1, meta description alignment
7. INVOKE copywriting -> draft hero with all loaded context:
- Headline: benefit-first, confident, no hedge words
- Subhead: specific outcome ("15 minutes instead of 4 hours")
- CTA: imperative mood ("Schedule Your Diagnostic" not "Learn More")
8. INVOKE hq-brand-review -> score voice attributes, scan banned terms
9. Score 27/30 (Brand-Clear) -> present to user
(If 18: revise flagged items -> re-review -> present when >= 25)
After classifying the content type and identifying required skills, create this checklist:
hq-brand-review invoked on final outputWriting First, Enforcing Later: Starting to write content before invoking this skill and loading brand voice. By the time you realize the content is off-brand, you've committed 500+ tokens to text that needs rewriting. Load brand voice FIRST, write SECOND. The 30 seconds to load the guide saves 5 minutes of revision.
Skipping CRO for "Simple" Pages: Every client-facing page has a conversion goal, even if it's just "keep reading." A contact form without form-cro guidance converts 20-40% worse than one built with CRO patterns. No page is too simple for conversion optimization.
Brand Review as Optional: Treating hq-brand-review as a nice-to-have instead of a mandatory gate. AI-generated content introduces an average of 3-5 banned patterns per 500 words (hedge words, filler transitions, enthusiasm inflation). The review catches what you cannot see in your own output.
Using Generic Copywriting for Everything: The copywriting skill optimizes for persuasion. API docs need documentation-templates. Technical proposals need writing-clearly-and-concisely. Emails need cold-email or email-sequence. Using the wrong skill produces content that reads well but serves the wrong purpose.
Forgetting Pricing/Service Docs for Proposals: Proposals and SOWs that don't reference pricing-structure.md and service-definitions.md risk quoting wrong prices, using outdated service names, or missing required scope items. These docs change -- always load the current version.
One-Shot Content Without Iteration: Writing content in a single pass and presenting it as final. Professional content goes through: draft (with skills) -> brand review -> revision -> re-review. Skipping the revision cycle produces content that scores 15-20 (Revision Required) instead of 25+ (Brand-Clear).
Batch-Skipping for "Efficiency": "I'll write all 5 pages first, then brand-review them all at once." Each page has different content types and different skill requirements. Batch-reviewing produces generic feedback. Review each piece individually as it's completed.
Ignoring Channel-Specific Tone: A LinkedIn post at formality 3/10 and a client proposal at formality 6/10 require different approaches even though both are "content." The brand-quick-ref.md includes tone modulation by channel. Match the channel, not just the brand.
Mixed content (email with embedded landing page link preview): Treat each component by its own type. The email body follows email skills. The link preview / OG tags follow landing page skills. Score each component independently.
Content that updates existing copy (not writing from scratch): Still invoke the enforcer. Existing copy may already be off-brand. Load brand voice, review the existing copy against it, then make changes that move toward compliance -- not just the specific edit requested.
Urgent content ("just send it, we'll fix it later"): The enforcer still applies but can be compressed: load brand-quick-ref.md, do a rapid banned-term scan, verify the CTA is clear, and ship. "Later" never comes -- review before sending.
Content for a different brand (client's brand, not Sharkitect): This enforcer is for Sharkitect brand only. If writing content in a client's voice, do NOT apply Sharkitect brand rules. Use the client's brand guide if available, or the general copywriting skill.
development
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.
testing
--- name: using-sharkitect-methodology description: Use when starting any conversation in a Sharkitect workspace OR before any task involving NEW pricing, positioning, proposal, strategy, plan-execution, or schema-design work — mandates invocation of Sharkitect-specific methodology skills (pricing-strategy, marketing-strategy-pmm, smb-cfo, hq-revenue-ops, executing-plans, brainstorming) under the same anti-rationalization discipline as using-superpowers. Documentation has failed 4 times across H
testing
Use when user says 'end session', 'wrap up', 'stop for the day', 'done for today', 'close out', 'save session', 'wrapping up', or invokes /end-session. Runs the full 9-step end-of-session protocol: resource audit, MEMORY.md update, lessons capture, plan status, pending items, workspace checklist, .tmp/ audit, git commit+push, Supabase brain sync, session brief, summary. Final step schedules a detached self-kill of the current session ONLY (3s delay) so the window closes cleanly. Other claude.exe processes (active workspaces) are NOT touched -- orphan cleanup is handled separately by Claude-Orphan-Cleanup-Hourly with proper age safeguards. Do NOT use for: mid-session quick saves (use session-checkpoint), skill syncing (use sync-skills.py), brain memory queries (use supabase-sync.py pull), document freshness reviews (use document-lifecycle), resource gap detection (use resource-auditor).
testing
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.