founder-linkedin-language

Loads founder voice rules from LinkedIn YAML sources before drafting form rows and copy.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill founder-linkedin-language-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: founder-linkedin-language
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/founder-linkedin-language
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill founder-linkedin-language-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting founder-facing form rows, hub copy, or LinkedIn posts without the approved voice leads to inconsistent terminology, forbidden phrases slipping in, and off-brand public messaging. This Skill enforces a single source of truth for founder language before any writing begins. ## Core Features & Use Cases - Voice Source Loading: Reads linkedin-voice.yaml, dictionary.yaml, forbidden.yaml, and phrase-corpus.yaml from disk in a fixed order before drafting. - Form Row Rules (FR-FORM): Enforces plain-English card content for M1 Canvas form rows, banning internal jargon like §OPEN_QUESTIONS or hub terminology. - Locked Public Voice: Provides the exact approved headline, category line, product names, and perimeter statement for LinkedIn and outbound copy. - Terminology Sync: Runs sync_founder_linkedin_voice_v1.py to regenerate FORM_TERMINOLOGY_REQUIRED and the form receipt after terminology changes. - Use Case: Before writing a new M1 form row, load this Skill to confirm the wording matches the founder dictionary, contains no forbidden FT-* phrases, and reads standalone without chat context. ## Quick Start Load the founder LinkedIn language sources and check my draft form row against the forbidden phrase list before I submit it on Canvas.

Frequently Asked Questions about founder-linkedin-language

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write M1 Canvas form rows in the founder's voice?

Load the founder language sources from disk first: linkedin-voice.yaml, dictionary.yaml, forbidden.yaml, and phrase-corpus.yaml. Write plain-English case stories on the card, avoid internal codes like §OPEN_QUESTIONS, and confirm locally before submitting on Canvas.

What is the approved LinkedIn headline and product naming?

The locked headline is "AI Governance & RWA Infrastructure Architect | Pre-Execution Risk & Compliance". Approved product names are Trust Brief, Evidence-Grade Audit Engine, Policy Replay, and Pre-Execution Regulatory Pack, with the perimeter: no custody, no payment initiation, advisory only.

How do I check for forbidden phrases before publishing copy?

Read forbidden.yaml from the founder-language attachments directory and verify the draft contains no FT-* phrases. The Skill's say checklist requires this check plus confirming the form row reads standalone without opening another chat.

What should I run after changing form terminology?

Run python3 scripts/sync_founder_linkedin_voice_v1.py after any terminology change. It regenerates the M1 Canvas FORM_TERMINOLOGY_REQUIRED block and the form receipt so the form stays aligned with the founder voice sources.

When should this Skill not be used?

It is scoped to founder-facing language: form rows, hub copy, LinkedIn posts, and founder notes interpretation. It does not apply to internal engineering documentation, code changes, or content unrelated to the founder's public voice and terminology.