X Algorithm Post Writing
carson2222/skills
Writes and reviews X posts, threads and replies using what the open-sourced For You ranking system rewards, and explains why a post may have underperformed.
Writes a short Twitter/X post that promotes a ForgeCode feature, built to sit beside an attached demo video, and shows it for your approval.
Install ForgeCode Feature Post Writer
$ npx skills add tailcallhq/forgecode --skill post-forge-feature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tailcallhq/forgecode post-forge-feature --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/tailcallhq/forgecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.forge/skills/post-forge-feature .claude/skills/post-forge-feature && 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 "post-forge-feature" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/post-forge-feature into .claude/skills/post-forge-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-forge-feature", 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/tailcallhq/forgecode/tree/main/.forge/skills/post-forge-featureType 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 tailcallhq/forgecode --skill post-forge-feature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tailcallhq/forgecode post-forge-feature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.forge/skills/post-forge-feature .agents/skills/post-forge-feature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "post-forge-feature" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/post-forge-feature into .agents/skills/post-forge-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-forge-feature", 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 tailcallhq/forgecode --skill post-forge-feature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tailcallhq/forgecode post-forge-feature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.forge/skills/post-forge-feature .cursor/skills/post-forge-feature && 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 "post-forge-feature" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/post-forge-feature into .cursor/skills/post-forge-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-forge-feature", 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/tailcallhq/forgecode.git --path .forge/skills/post-forge-feature--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 tailcallhq/forgecode --skill post-forge-feature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tailcallhq/forgecode post-forge-feature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.forge/skills/post-forge-feature .gemini/skills/post-forge-feature && 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 "post-forge-feature" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/post-forge-feature into .gemini/skills/post-forge-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-forge-feature", 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 tailcallhq/forgecode post-forge-featureInstalls 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 tailcallhq/forgecode --skill post-forge-feature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .github/skills && cp -r skills-src/.forge/skills/post-forge-feature .github/skills/post-forge-feature && 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 "post-forge-feature" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/post-forge-feature into .github/skills/post-forge-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-forge-feature", 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 tailcallhq/forgecode --skill post-forge-feature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tailcallhq/forgecode post-forge-feature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.forge/skills/post-forge-feature .opencode/skills/post-forge-feature && 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 "post-forge-feature" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/post-forge-feature into .opencode/skills/post-forge-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-forge-feature", 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
post-forge-feature- GitHub stars
- 7.6k
- Token cost
- ~374 tokens
- SKILL.md length
- 178 words
- Files
- 2 (incl. references)
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Writes a short Twitter/X post that promotes a ForgeCode feature, built to sit beside an attached demo video, and shows it for your approval.
- Works in 3 steps: Understand the feature: use tools to… → Craft the post: follow the constraints… → Present for approval: show the post and…
- Writing a tweet about a new ForgeCode feature
- SKILL.md covers Workflow, Key Constraints and Reference Files
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The agent first reads the relevant source code, docs or changelog to learn what the feature does, when a developer would reach for it and what pain it removes. It then drafts the post using the style guide in references/style-guide.md, which sets tone, vocabulary, approved hashtags and example posts, and presents the draft for tweaks before finalizing.
Constraints keep posts tight: two to three sentences that fit roughly 280 characters, no filler announcement phrases, no em dashes, the name written as ForgeCode, a lead that states the developer benefit or problem solved, and a closing hashtag line. Because the video is attached, the post neither tells readers to watch it nor describes what is in it.
When your agent uses it
- Writing a tweet about a new ForgeCode feature
- Promoting a ForgeCode release on social media with a demo video
- Rewriting a draft post to fit the ForgeCode style guide
Example prompts
- “Write a tweet for the new ForgeCode feature in the latest changelog entry.”
- “Draft an X post for the feature described in docs/features.md; I will attach the video.”
- “Tighten this post so it fits the style guide and ends with the approved hashtags.”
Requirements
- Access to the ForgeCode source, docs or changelog
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Understand the feature: use tools to read the relevant source code, docs, or changelogs. Answer
- Craft the post: follow the constraints in references/style-guide.md.
- Present for approval: show the post and ask if the user wants tweaks before finalizing.
What it can do on your machine
Read from SKILL.md and the folder at commit 92a5699. 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
ForgeCode Feature Post Writer loads about 374 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 178 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 tailcallhq/forgecode at commit 92a5699, republished under its Apache-2.0 licence (© tailcallhq). 178 words, ~374 tokens.
Download SKILL.mdSave it as
.claude/skills/post-forge-feature/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- post-forge-feature
- description
- Generate a Twitter/X post highlighting a Forge feature. Use when the user asks to write a tweet, create a Twitter post, or promote a ForgeCode feature on social media. The post always accompanies an attached video demonstrating the feature.
Post ForgeCode Feature
Generate a punchy, developer-friendly Twitter/X post for a ForgeCode feature. The post always accompanies a video, so no need to describe every detail; the video does the showing.
Workflow
Understand the feature: use tools to read the relevant source code, docs, or changelogs. Answer:
- What does it do?
- When would a developer reach for it?
- What pain does it remove?
Craft the post: follow the constraints in
references/style-guide.md.Present for approval: show the post and ask if the user wants tweaks before finalizing.
Key Constraints
- 2-3 sentences max (fits ~280 chars).
- No filler phrases ("excited to announce", "game changer", "introducing").
- Always refer to the product as "ForgeCode", never "Forge" alone.
- No em dashes anywhere in the post.
- Lead with the developer benefit or the problem solved, not the feature name.
- The video is attached. Do not say "watch the video" or describe what is in it.
- End with a relevant hashtag line (see style guide for approved tags).
Reference Files
references/style-guide.md: tone, vocabulary, approved hashtags, and example posts. Read this before drafting.
© tailcallhq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .forge/skills/post-forge-feature of tailcallhq/forgecode.
- SKILL.md
- references/style-guide.md
Open the folder on GitHubat commit 92a5699
Compare with similar skills
ForgeCode Feature Post Writer 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 |
|---|---|---|---|---|---|---|
| ForgeCode Feature Post Writer this skilltailcallhq/forgecode | 7.6k | — | ~374 | Automated safety check: Pass | Apache-2.0 | |
| X Algorithm Post Writingcarson2222/skills | 113 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Getxapi ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~715 | Automated safety check: Pass | Custom licence | |
| X Twitter ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~1.6k | Automated safety check: Pass | Custom licence | |
| Social Media Managementmanojbajaj95/claude-gtm-plugin | 104 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Twitter Intelligencesandbaseai/sandbase-skills | 201 | — | ~943 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
X Twitter Connect
LeoYeAI/openclaw-marketing-skills
Connect TweetClaw to pull public X/Twitter marketing signals into OpenClaw workflows.
Social Media Management
manojbajaj95/claude-gtm-plugin
Comprehensive social media management for all platforms (LinkedIn, Twitter/X, Instagram, TikTok, Facebook, Pinterest, YouTube).
Twitter Intelligence
sandbaseai/sandbase-skills
Search tweets, analyze trends, monitor users, and gather social intelligence from Twitter/X through SandBase.
Money Social
iamzifei/show-me-the-money
Social media management and community building automation. An agent skill from iamzifei/show-me-the-money.
More from tailcallhq/forgecode
All 14 skills in this repoGit Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
Forge CLI Debug Workflow
tailcallhq/forgecode
Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.
FIXME Resolver
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
Reasoning Serialization Tests
tailcallhq/forgecode
Checks that ReasoningConfig fields are serialized into the right provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot and Codex requests.
Implementation Plan Creator
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
Release Notes Writer
tailcallhq/forgecode
Pulls a GitHub release and every linked pull request, then writes polished, factual release notes from the combined set of changes.
Related
Works with
Categories
Questions about ForgeCode Feature Post Writer
What does ForgeCode Feature Post Writer do?
Writes a short Twitter/X post that promotes a ForgeCode feature, built to sit beside an attached demo video, and shows it for your approval. The agent first reads the relevant source code, docs or changelog to learn what the feature does, when a developer would reach for it and what pain it removes.md, which sets tone, vocabulary, approved hashtags and example posts, and presents the draft for tweaks before finalizing.
When should I use ForgeCode Feature Post Writer?
ForgeCode Feature Post Writer fits situations like: writing a tweet about a new ForgeCode feature; promoting a ForgeCode release on social media with a demo video; rewriting a draft post to fit the ForgeCode style guide.
How do I install ForgeCode Feature Post Writer in Claude Code?
Run `npx skills add tailcallhq/forgecode --skill post-forge-feature -a claude-code`. Or copy the skill folder (.forge/skills/post-forge-feature in tailcallhq/forgecode) into .claude/skills/post-forge-feature in your project. Claude Code loads it when a task matches its description.
How do I install ForgeCode Feature Post Writer in Codex?
Run `npx skills add tailcallhq/forgecode --skill post-forge-feature -a codex`. Or copy the skill folder (.forge/skills/post-forge-feature in tailcallhq/forgecode) into .agents/skills/post-forge-feature in your project. Codex loads it when a task matches its description.
Can I use ForgeCode Feature Post Writer 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 tailcallhq/forgecode --skill post-forge-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-forge-feature, .gemini/skills/post-forge-feature, .github/skills/post-forge-feature and .opencode/skills/post-forge-feature in your project.
What does ForgeCode Feature Post Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: ForgeCode Feature Post Writer is instructions for the agent only. Our summary lists: Access to the ForgeCode source, docs or changelog.
Does ForgeCode Feature Post Writer 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 ForgeCode Feature Post Writer 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 ForgeCode Feature Post Writer use?
ForgeCode Feature Post Writer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does ForgeCode Feature Post Writer use?
About 374 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 695 tokens, read only when the agent opens those files.
What are the alternatives to ForgeCode Feature Post Writer?
Skills that share tags, products or a category with ForgeCode Feature Post Writer: X Algorithm Post Writing (carson2222/skills, 113 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), X Twitter Connect (LeoYeAI/openclaw-marketing-skills, 1k stars) and Social Media Management (manojbajaj95/claude-gtm-plugin, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains ForgeCode Feature Post Writer?
tailcallhq (a GitHub organization) maintains it in tailcallhq/forgecode, which has 7,642 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: tailcallhq/forgecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.