Exact source text
No edits · 4,603 bytes
Skill Source

ForgeFX Social Posts

The complete, exact text of the active forgefx-social-posts skill file, rendered verbatim for review.

SKILL.mdMarkdown · UTF-8
---
name: forgefx-social-posts
description: Draft and review ForgeFX LinkedIn posts, comments, and reshare captions for ForgeFX team members. Use whenever someone asks for ForgeFX social copy, a LinkedIn comment, a repost caption, an event post, or wants copy matched to Kristen Cox’s established voice. Keep each leader’s voice distinct and ground every claim, date, name, and event detail in the supplied source.
---

# ForgeFX Social Posts

Create paste-ready social copy that sounds like the named ForgeFX team member, not like the ForgeFX company page and not like another executive.

## Source discipline

1. Read the supplied post, screenshot, link, or brief before drafting.
2. Preserve exact names, event year, dates, location, technologies, and claims from the source.
3. Never invent partner names, attendee names, relationships, metrics, or event participation.
4. Treat the embedded company post as context. Personal comments and reshare captions should add perspective rather than paraphrase it.
5. If the post already communicates the product benefits, do not repeat those benefits in the personal caption.

## Output format

When asked for both, return these two labeled blocks:

**Post comment**

[One paste-ready preferred comment]

**Reshare caption**

[One paste-ready preferred caption]

Return one strong version by default. Provide alternatives only when requested. Keep explanation out of the copy blocks.

## Distinct personal voices

Do not let multiple ForgeFX leaders sound interchangeable. Check for stock openings and repeated phrasing before finalizing.

### Kristen Cox

Kristen’s LinkedIn voice is practical, relationship-first, concise, and low-hype. Read `references/kristen-cox-linkedin-voice.md` whenever drafting or reviewing copy for her. It contains her confirmed constraints, approved published examples, and the lessons from prior revisions.

#### Comments on ForgeFX posts

- Add a human or relationship-centered perspective instead of summarizing the company post.
- Prefer partners, peers, shared work, useful conversations, and the people who help programs succeed.
- Mention relevant people when Kristen supplies their names or the source proves the relationship. Never invent tags.
- Keep the comment to one or two sentences unless Kristen asks for more.
- Sound conversational and professional. A natural sentence fragment can be acceptable when it improves authenticity.
- Do not turn the comment into a ForgeFX capabilities pitch. Personalize through relationships and shared conversations, not product benefits.
- Inspect visible comments when available and avoid openings or sentence patterns already used by Greg, Dave, or another ForgeFX leader.
- Do not open with “Excited” or “Looking forward.”
- Do not use em dashes.

#### Reshare captions

- Keep the caption shorter than the embedded company post.
- Lead with the concrete event or business fact.
- Identify the specific audience that would benefit from connecting.
- Use a straightforward invitation rather than promotional hype.
- Default to one or two short paragraphs and no more than five focused hashtags.
- Avoid repeating benefits already visible in the embedded post or graphic.
- Do not use em dashes.

### Other ForgeFX leaders

When a leader-specific profile is not yet documented:

1. Use examples supplied by that person as the strongest evidence.
2. Avoid openings or sentence patterns already associated with another leader.
3. Keep the draft restrained and ask for voice feedback after showing the preferred version.
4. Add durable voice rules to this skill only after the person confirms them.

## Comment versus reshare

A post comment participates in the existing conversation. It should add one useful human angle, relationship, observation, or reaction.

A reshare caption introduces the post to a different network. It should explain why that network should care or who should connect, without reproducing the source post.

Do not use the same opening, central sentence, or closing in both outputs.

## Final review

Before returning copy, verify:

- The comment and reshare serve different purposes.
- The named person’s voice is distinct from other ForgeFX leaders.
- No unsupported names, claims, dates, or relationships were added.
- The copy does not restate the embedded post.
- The tone is natural rather than sales-heavy.
- Kristen’s copy contains no em dashes and does not open with “Excited” or “Looking forward.”
- Hashtags are relevant, focused, and limited to five unless the user requests otherwise.
- The result is paste-ready.