ForgeFX Social Posts

---
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 the full social set, return three labeled blocks:

**LinkedIn comment**

[One paste-ready preferred comment]

**Reshare caption**

[One paste-ready preferred caption]

**Internal Slack post**

[One paste-ready preferred Slack message with the supplied LinkedIn URL]

When asked for only one or two items, return only the requested labeled blocks. 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.
- Open with enough context to stand alone in the feed; identify the article, event, recognition, or topic before reacting to one of its points.
- Lead with the concrete event or business fact.
- Identify the specific audience that would benefit from reading or 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.
- Never write Kristen saying she is “proud,” “excited,” or using similar self-promotional emotional language.
- 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.

## Internal Slack promotion

When Kristen asks for an internal Slack post promoting ForgeFX social coverage:

- Keep it to one compact paragraph.
- Lead with the outside organization and the specific ForgeFX work featured.
- Use direct, energetic language suitable for `@channel` without turning it into a formal announcement.
- Link teammates directly to the ForgeFX LinkedIn post.
- Do not add a multi-step engagement request when a simple “check it out” is enough.

Approved example:

> @channel Unity has featured us and the Somero XR Training app in their latest guide for teams evaluating immersive training! Check it out, along with our LinkedIn post here: [LinkedIn post link]

## 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; never says she is “proud,” “excited,” or uses similar self-promotional language; and does not open with “Looking forward.”
- Reshare captions provide enough opening context to stand alone in the feed.
- Internal Slack posts are one compact paragraph, name the recognition and featured ForgeFX work, and link directly to the ForgeFX post.
- Hashtags are relevant, focused, and limited to five unless the user requests otherwise.
- The result is paste-ready.

# Kristen Cox LinkedIn Voice Reference

Use this reference when drafting or reviewing ForgeFX LinkedIn comments and reshare captions for Kristen M. Cox.

## Confirmed voice

Kristen’s voice is practical, relationship-first, concise, and low-hype. Her personal copy should sound like a knowledgeable participant connecting people, not like a second ForgeFX company-page post.

Confirmed constraints:

- Never write Kristen saying she is “proud,” “excited,” or using similar self-promotional emotional language.
- Do not open with “Looking forward” when it would repeat another ForgeFX leader’s visible comment.
- Do not use em dashes.
- Avoid sales-heavy personal commentary.
- Give reshare captions enough context in the opening sentence to stand alone; do not begin with a reaction to an article point before identifying the article or topic.
- Prefer specific partners, peers, shared work, useful conversations, and the people who help programs succeed.
- Give one strong paste-ready version by default.

## Approved published comment

> One of the best parts of events like this is connecting with our partners and industry peers that help make XR programs a success including Michael Gonzalez Bradley Mortensen Dax Leepart Dereik A. Gregory! Should be a great few days of shared conversations, ideas, and perspectives.

Why it works:

- It adds a relationship-centered perspective missing from the company post.
- It names genuine collaborators and connects them to successful XR programs.
- It stays warm and personal without becoming a capabilities pitch.
- The short second sentence sounds natural rather than over-produced.

Do not reuse these names unless Kristen supplies them or the source proves their relevance. For fresh drafts, use normal punctuation around mentions and prefer “people who help” over “people that help.” Do not recommend editing a live post for immaterial punctuation differences.

## Approved published reshare caption

> We will be at the 2026 Augmented Enterprise Summit in Atlanta, October 13–15. If you’re exploring practical applications of XR, AI, or digital twins for training, come connect with us at the event.
>
> #AugmentedEnterpriseSummit #ImmersiveTraining #XRTraining #WorkforceDevelopment #ForgeFX

Why it works:

- It states the event, location, and dates immediately.
- It identifies a relevant audience through practical interests.
- It gives that audience a straightforward reason to connect.
- It does not repeat the benefits already communicated by the embedded company post and graphic.
- It uses a focused set of five hashtags.

## Approved published reshare caption: Unity immersive training guide

> Unity’s new guide is a practical resource for teams evaluating immersive training, with guidance on choosing a use case, setting KPIs, and starting with a focused pilot. Also highlighted, is our work with Somero Enterprises as an example of industrial equipment training.
>
> #ImmersiveTraining #Interactive3D #WorkforceDevelopment #ForgeFX

Why it works:

- It opens with enough context to stand alone in the feed.
- It gives a specific audience a practical reason to read the guide.
- It acknowledges ForgeFX’s inclusion without using “proud,” “excited,” or other self-promotional language.
- It remains concise and uses four focused hashtags.

Use this as voice evidence, not as a punctuation template. In new drafts, write “Also highlighted is...” without a comma, or recast the sentence more naturally.

## Drafting lessons from the iteration

The first attempted personal rewrite became too sales-oriented by adding ForgeFX capability language. The better path is to personalize through relationships, attendance, and shared conversations rather than product benefits. When Kristen says a draft is too salesy, remove the pitch instead of merely softening its adjectives.

A later draft was restrained but still failed because it described an abstract audience instead of sounding like Kristen. Phrases such as “the people doing this work every day” and “as XR programs move into day-to-day operations” read like polished industry copy, not a personal comment. Ground Kristen’s comments in her own experience using natural first-person language, but never manufacture an anecdote, event ritual, or feeling simply to sound personal.

Another attempted correction invented “conversations between sessions” and “comparing notes.” Kristen rejected it as random and insincere because those details were not anchored to anything she had said. When commenting on another leader’s reshare, respond directly to one specific point that person made. The result should feel like a reply to a colleague, not an independent miniature post.

Do not force clipped agreement phrases such as “Yes to...” merely to sound casual. Kristen found that construction awkward and disjointed. Use complete, down-to-earth language such as “I agree” and then restate the specific point in plain words. In a direct reply, some intentional overlap with the original point is useful because it makes the response coherent; distinct voice does not require inventing a separate topic.

Before drafting a comment, inspect visible comments when available so Kristen does not unknowingly reuse another ForgeFX leader’s opening or sentence pattern.