skills/legal-advertorial-writer/SKILL.md
Writes legal-tech advertorials, landing pages, and blog-to-CTA copy for expungement, debt relief, housing rights, and related services. Use when turning educational legal content into honest, trauma-informed conversion copy with clear competitive framing and non-hyped CTAs. NOT for legal advice, courtroom filings, or manipulative direct-response copy that overstates results.
npx skillsauth add curiositech/windags-skills legal-advertorial-writerInstall 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.
The central premise: readers are not marks — they are people with a problem looking for a solution. Legal products serve people at vulnerable moments. Overselling destroys trust and conversions. Honesty earns both.
The advertorial format works because it educates first and sells second. When the reader arrives at the CTA, they already understand why the product exists and whether it solves their specific problem. The sale is the natural conclusion of the article, not a pitch bolted onto the end.
Every advertorial article follows this structure:
Lead with the reader's actual experience, not a statistic. Name the specific frustration or confusion they're feeling. Make them feel seen before you educate them.
This is genuine, accurate information. It earns trust and does most of the selling. The reader should leave knowing something true and useful whether or not they buy.
Briefly describe what options exist — including free/DIY options. Acknowledge their tradeoffs. Don't trash competitors; compare honestly.
Readers who understand their options and still choose your product are your best customers.
After a well-built article, the CTA should feel like a natural conclusion, not a pivot. Keep it short. One sentence of reinforcement, one action.
Template CTA block structure:
[One sentence that closes the article's argument and connects it to the product]
[What you get + price, stated plainly]
[Button: action-oriented, specific, honest]
Legal advertorials must thread a needle between useful information and unauthorized practice of law (UPL).
Safe patterns:
Avoid:
For legal tech products, readers typically compare against:
| Option | Cost | Effort | When it's right | |--------|------|--------|-----------------| | DIY | Free–$50 | High | Simple cases, patient users | | Legal aid nonprofits | Free | Waitlist 2–6 months | Best for complex/serious cases | | Private attorney | $1,500–$5,000 | Low | Complex cases, high stakes | | Legal tech products | $19–$199 | Low–medium | Middle: too complex for DIY, not complex enough for attorney |
Honest positioning: legal tech lives in the middle. Acknowledge this. Never claim to replace an attorney.
references/advertorial-patterns.md — Annotated examples of effective and ineffective legal advertorial copy with commentaryreferences/cta-templates.md — CTA block templates for different product types and emotional contextsflowchart TD
A[Incoming request for Legal Advertorial Writer] --> B{Within this skill's scope?}
B -->|No| C[Redirect using NOT-for boundaries]
B -->|Yes| D[Assess inputs, constraints, and current state]
D --> E{Which path fits best?}
E -->|Plan or design| F[Choose the simplest viable pattern]
E -->|Migration or change| G[Protect compatibility and rollout safety]
E -->|Debug or evaluate| H[Localize the failing boundary first]
F --> I[Apply the domain-specific guidance below]
G --> I
H --> I
I --> J[Validate against the quality gates]
Use this as the first-pass routing model:
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.