agentleFS
sophonfinance-wqsophonfinance-wq/finance-automation-portfolio/.claude/skills/linkedin-post/SKILL.md

linkedin-post

Skill16 starsChanged 44 days agoMITView on GitHub

Draft LinkedIn posts for Sophon Finance Systems in the founder's voice (hard opener, background for credit, non-AI style). Use for any social/announcement copy.

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use linkedin-comment, instagram-post and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • cavalenzuelalaraSkill

    linkedin-comment

    Redacta comentarios profesionales y estratégicos para publicaciones de LinkedIn, personalizados según el perfil y experiencia del usuario. Activar ÚNICAMENTE cuando el mensaje contenga alguna de estas frases exactas (con o sin tilde): "linkedin comment", "comentario linkedin", "comentarios linkedin". No activar ante relatos o situaciones descritas sin uno de estos triggers. Funciona en español e inglés según el idioma del usuario o su indicación explícita.

    Also in 3 projects that use this

  • runehub-aiSkill

    instagram-post

    Publish a photo or reel on Instagram via Graph API.

    Also in 3 projects that use this

  • runehub-aiSkill

    youtube-upload

    Upload a video to YouTube.

    Also in 3 projects that use this

  • ncklrsSkill

    proposal-writer

    Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 3 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Kill the AI smell: no em-dashes, no emoji-bulleted feature lists, no "it didn't remove X, it moved X" chiasmus slogans, no rule-of-three …

    line 9
  2. Distinctive:

    Always pair with a house-style graphic (see the brand-graphics skill).

    line 13

“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LinkedIn Posts — Founder Voice

Voice rules (non-negotiable, learned by iteration)

  • Hard opener: a blunt claim or contrarian line, then credentials for credit: "18 years closing the books for Fortune 100 and 500 companies." Name: Sophonnarith Hang, senior accounting & tax, GAAP/FAR/CAS.
  • Kill the AI smell: no em-dashes, no emoji-bulleted feature lists, no "it didn't remove X, it moved X" chiasmus slogans, no rule-of-three punchlines, no title-case headers. Short, uneven sentences. Contractions.
  • Max 3 hashtags, lowercase: #finance #accounting #ai.
  • Links: site (sophonfinance.com) + email (contact@sophonfinance.com) in body; GitHub link works better as the FIRST COMMENT (body links get reach-throttled) — but follow the user's explicit ask if they want it in-body.
  • End with a soft CTA: "If your close still eats a week, message me. I'll show you what I'd automate first, free."
  • Always pair with a house-style graphic (see the brand-graphics skill). Deliver copy in a code block for easy copy-paste.
  • Claims must be true to the repo: cite real test counts, real demo output, "fictional data, run it yourself".

Cadence content on file

references/post-series.md (in this skill's folder) holds the ready-to-paste series: launch + one post per engine. Already published: the self-healing launch post (with the tie-out diagram) and "One loop architecture. Five gate policies." (with the gate-policy table).

Posts 2-6 predate these voice rules (em-dashes, Title-Case hashtags) — rewrite them into the voice above before delivering. Posts 7-15 (engines 39-47) are already in this voice and lint clean — deliver them as-is; each carries its GitHub first comment beside it. Continue numbering from 16.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.