agentsclimarketplace

Editorial articulation

Skill frankxai/starlight-design-intelligence/skills/editorial-articulation

Owned premium design intelligence: brand packs, motion systems, UI rubrics, and visual identity doctrine for FrankX, Starlight, and Arcanea.

Install
npx -y skills add frankxai/starlight-design-intelligence --skill editorial-articulation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when writing or reviewing high-value web language, especially partner pages, founder sites, homepages, launch pages, product narratives, and personal invitations that must sound observed, specific, and human rather than generically AI-generated.

SKILL.md

2.1 KB, 398 tokens by cl100k_base, as published. Nobody here has run it

Editorial Articulation

The reader should feel observed, not segmented; addressed, not processed; shown proof, not asked to admire architecture.

Five Facts Before Drafting

  1. Recipient: exact person or buying moment.
  2. Prior state: what they already know, believe, fear, or reject.
  3. Observed truth: a moment, behavior, artifact, quotation, or result that earned the page.
  4. Proposition: the smallest credible change being offered.
  5. Consequence: what the reader can do, decide, own, or stop.

If observed truth is missing, research or ask. Never simulate intimacy.

First 120 Words

Establish why the page exists, what was actually observed, the smallest proposition, and why the reader should continue. Do not lead with the builder's ecosystem, repository stack, worldview, or category thesis.

Sentence Posture

  • Put actor and verb early.
  • Prefer inspectable nouns: recording, source file, decision, prototype, reply.
  • Translate internal taxonomy after the value is understood.
  • Make one turn of thought per paragraph.
  • Vary sentence length deliberately.
  • Let confidence come from selection and evidence, not intensifiers.
  • Read the page aloud at speaking pace.

Blocking Tests

  • Name swap: if another person's name fits unchanged, rewrite.
  • Builder taxonomy: if the first 120 words rely on AI, agent, skill, infrastructure, ecosystem, sovereign, substrate, or graph, rewrite.
  • Concrete anchor: every major section needs an inspectable anchor.
  • Deletion: remove the cleverest line; if the page improves, keep it removed.
  • Independent verdict: a non-author must identify the recipient, observation, proposition, most generated line, and unnecessary line without vague answers.

Never invent quotation, praise, partnership, fit, consent, authority, or endorsement.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.