linkedin-post

Generate a reviewable LinkedIn post draft grounded in current project documentation and evidence.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill linkedin-post-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linkedin-post
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/linkedin-post
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill linkedin-post-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing an accurate LinkedIn post about a technical project requires gathering current status, recent changes, and supporting evidence from across the repository, which is slow and error-prone. This Skill automates that research and produces a factual draft saved to reports/linkedin-post-draft.md for human review. ## Core Features & Use Cases - Evidence-grounded drafting: Reads the project handoff, project guide, README, architecture docs, and validation reports so every material claim is backed by current evidence. - Update posts from history: With the --update flag, compares against reports/linkedin-post-history.md to describe only verified new features, milestones, or lessons since the last post. - Tone and audience control: Supports --technical, --executive, and --community tones, with drafts flagged for claims requiring user review such as metrics, links, or internal names. - Use Case: After shipping a new release, run the skill with --update to produce a draft highlighting only the verified changes since your last published post, then review and publish it yourself. ## Quick Start Ask the agent to run /linkedin-post --update --community to draft a LinkedIn update post based on verified changes since the last recorded post.

Frequently Asked Questions about linkedin-post

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

FAQPage Schema
How do I draft a LinkedIn post about my software project?

Run the skill with /linkedin-post to analyze your repository's handoff, project guide, README, and recent changes. It writes a factual draft to reports/linkedin-post-draft.md that you review and approve before publishing manually.

How do I write a LinkedIn update post about recent project changes?

Use the --update flag so the skill reads reports/linkedin-post-history.md and describes only verified new features, improvements, or milestones since the last recorded post. If no history exists, it asks before preparing a first-post draft.

Can this skill publish directly to LinkedIn?

No, the skill only produces a draft file and never publishes, schedules, or sends content to LinkedIn or any external service. Publication requires your explicit separate approval and manual action outside the skill.

What tones are supported for LinkedIn post drafts?

Three tones are supported via flags: --technical, --executive, and --community. The default is a community-focused, technically accessible tone aimed at Microsoft employees and the broader technical community.

Does the skill prevent confidential information in LinkedIn drafts?

Yes, the skill excludes secrets, credentials, private URLs, personal data, and unsupported claims from drafts. It also lists claims requiring your review, such as internal names, metrics, and links, before you approve the content.