Social
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
Write a LinkedIn post based on research findings or a given topic.
Install Linkedin Post
$ npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install langchain-ai/langgraph-101 linkedin-post --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/langchain-ai/langgraph-101.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/deep_agent/skills/linkedin-post .claude/skills/linkedin-post && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linkedin-post" agent skill from https://github.com/langchain-ai/langgraph-101/tree/main/agents/deep_agent/skills/linkedin-post into .claude/skills/linkedin-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/langchain-ai/langgraph-101/tree/main/agents/deep_agent/skills/linkedin-postType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install langchain-ai/langgraph-101 linkedin-post --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langchain-ai/langgraph-101.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agents/deep_agent/skills/linkedin-post .agents/skills/linkedin-post && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linkedin-post" agent skill from https://github.com/langchain-ai/langgraph-101/tree/main/agents/deep_agent/skills/linkedin-post into .agents/skills/linkedin-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install langchain-ai/langgraph-101 linkedin-post --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langchain-ai/langgraph-101.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agents/deep_agent/skills/linkedin-post .cursor/skills/linkedin-post && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linkedin-post" agent skill from https://github.com/langchain-ai/langgraph-101/tree/main/agents/deep_agent/skills/linkedin-post into .cursor/skills/linkedin-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/langchain-ai/langgraph-101.git --path agents/deep_agent/skills/linkedin-post--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install langchain-ai/langgraph-101 linkedin-post --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langchain-ai/langgraph-101.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agents/deep_agent/skills/linkedin-post .gemini/skills/linkedin-post && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linkedin-post" agent skill from https://github.com/langchain-ai/langgraph-101/tree/main/agents/deep_agent/skills/linkedin-post into .gemini/skills/linkedin-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install langchain-ai/langgraph-101 linkedin-postInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/langchain-ai/langgraph-101.git skills-src && mkdir -p .github/skills && cp -r skills-src/agents/deep_agent/skills/linkedin-post .github/skills/linkedin-post && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-post" agent skill from https://github.com/langchain-ai/langgraph-101/tree/main/agents/deep_agent/skills/linkedin-post into .github/skills/linkedin-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install langchain-ai/langgraph-101 linkedin-post --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langchain-ai/langgraph-101.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agents/deep_agent/skills/linkedin-post .opencode/skills/linkedin-post && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-post" agent skill from https://github.com/langchain-ai/langgraph-101/tree/main/agents/deep_agent/skills/linkedin-post into .opencode/skills/linkedin-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linkedin-post- GitHub stars
- 679
- Token cost
- ~492 tokens
- SKILL.md length
- 103 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a LinkedIn post based on research findings or a given topic.
- Asked to create LinkedIn content
- SKILL.md covers Format, Tone, Length and Template, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Professional posts
What it does
Linkedin Post is an agent skill from langchain-ai/langgraph-101, published by the product's own GitHub organization. Write a LinkedIn post based on research findings or a given topic. Use this skill when asked to create LinkedIn content, professional posts, or thought leadership pieces.
Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Social media posts. It works with LinkedIn. The repository describes itself as: Learn about the fundamentals of LangGraph through a series of notebooks. The licence is MIT.
When your agent uses it
- Asked to create LinkedIn content
- Professional posts
- Thought leadership pieces
Example prompts
- “/linkedin-post”
What it can do on your machine
Read from SKILL.md and the folder at commit 508ef15. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Linkedin Post loads about 492 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 103 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from langchain-ai/langgraph-101 at commit 508ef15, republished under its MIT licence (© langchain-ai). 103 words, ~492 tokens.
Download SKILL.mdSave it as
.claude/skills/linkedin-post/SKILL.md (or your agent's skills folder).- name
- linkedin-post
- description
- Write a LinkedIn post based on research findings or a given topic. Use this skill when asked to create LinkedIn content, professional posts, or thought leadership pieces.
LinkedIn Post Skill
Format
- Hook: Start with a bold opening line that grabs attention (this appears before the "see more" cut)
- Body: 3-5 short paragraphs, each 1-2 sentences
- Use line breaks between paragraphs for readability
- Include 1-2 relevant emojis per paragraph (don't overdo it)
- End with a call-to-action or question to drive engagement
- Add 3-5 relevant hashtags at the bottom
Tone
- Professional but conversational
- Share insights, not just information
- Use "I" statements and personal perspective where appropriate
- Avoid jargon unless the audience expects it
Length
- Ideal: 150-300 words
- LinkedIn truncates after ~210 characters, so the first line must hook the reader
Template
[Bold hook / surprising stat / question]
[Context -- why this matters]
[Key insight 1]
[Key insight 2]
[Key insight 3 or personal takeaway]
[Call to action / question for engagement]
#hashtag1 #hashtag2 #hashtag3Example
Most AI agents fail not because of the model -- but because of context management.
After researching the latest agent frameworks, one pattern keeps emerging:
the best agents treat their context window like a scarce resource.
Here's what separates good agents from great ones:
1. They offload intermediate results to a filesystem instead of keeping everything in context
2. They delegate to subagents for isolation -- the main agent only sees summaries
3. They use progressive disclosure -- loading instructions only when relevant
The shift from "bigger context window" to "smarter context management" is where
the real breakthroughs are happening.
What patterns have you seen work best in your agent architectures?
#AIAgents #LangChain #LangGraph #ContextEngineering© langchain-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in agents/deep_agent/skills/linkedin-post of langchain-ai/langgraph-101.
Open the folder on GitHubat commit 508ef15
Compare with similar skills
Linkedin Post next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linkedin Post this skilllangchain-ai/langgraph-101 | 679 | — | ~492 | Automated safety check: Pass | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Social Contentfreekmurze/dotfiles | 1k | 23 repos | ~2.1k | Automated safety check: Pass | None | |
| Linkedin Marketingsergebulaev/linkedin-skills | 4.3k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Typefullyfreekmurze/dotfiles | 1k | 2 repos | ~3.4k | Automated safety check: Notes | None | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.3k | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Social Content
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
Linkedin Marketing
sergebulaev/linkedin-skills
Plan, draft, audit, and publish LinkedIn posts and comments.
Typefully
freekmurze/dotfiles
Create, schedule, and manage social media posts via Typefully.
Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Changelog Social Recap
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
More from langchain-ai/langgraph-101
- Official
Twitter Post
langchain-ai/langgraph-101
Write a Twitter/X post or thread based on research findings or a given topic.
Related
Works with
Categories
Questions about Linkedin Post
What does Linkedin Post do?
Write a LinkedIn post based on research findings or a given topic. Linkedin Post is an agent skill from langchain-ai/langgraph-101, published by the product's own GitHub organization. Write a LinkedIn post based on research findings or a given topic.
When should I use Linkedin Post?
Linkedin Post fits situations like: asked to create LinkedIn content; professional posts; thought leadership pieces.
How do I install Linkedin Post in Claude Code?
Run `npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a claude-code`. Or copy the skill folder (agents/deep_agent/skills/linkedin-post in langchain-ai/langgraph-101) into .claude/skills/linkedin-post in your project. Claude Code loads it when a task matches its description.
How do I install Linkedin Post in Codex?
Run `npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a codex`. Or copy the skill folder (agents/deep_agent/skills/linkedin-post in langchain-ai/langgraph-101) into .agents/skills/linkedin-post in your project. Codex loads it when a task matches its description.
Can I use Linkedin Post in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add langchain-ai/langgraph-101 --skill linkedin-post -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin-post, .gemini/skills/linkedin-post, .github/skills/linkedin-post and .opencode/skills/linkedin-post in your project.
What does Linkedin Post need to run?
SKILL.md names no scripts, command-line tools or credentials: Linkedin Post is instructions for the agent only.
Does Linkedin Post access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Linkedin Post safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Linkedin Post use?
Linkedin Post is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linkedin Post use?
About 492 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Linkedin Post?
Skills that share tags, products or a category with Linkedin Post: Social (coreyhaines31/marketingskills, 54k stars), Social Content (freekmurze/dotfiles, 1k stars), Linkedin Marketing (sergebulaev/linkedin-skills, 4.3k stars) and Typefully (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linkedin Post?
langchain-ai (a GitHub organization, an official publisher) maintains it in langchain-ai/langgraph-101, which has 679 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 1, 2026.
Source: langchain-ai/langgraph-101 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.