Guide · Agent skill
How to use the Post ForgeCode Feature agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Post ForgeCode Feature skill is an agent skill that drafts a short, developer-friendly Twitter/X post promoting one ForgeCode feature. It is meant for maintainers and community staff who pair each feature with a demo video. By the end of this guide you will know what the skill does, how to install it, how to trigger it with a plain request, and where its limits are.
Quick start
- 1Download the ZIP. Download the post-forge-feature skill as a ZIP from this page.
- 2Unzip into a skills folder. Extract it to ~/.claude/skills/ for personal use, or to a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. In the Claude apps, open Settings, go to Capabilities, and upload the skill under Skills.
- 4Make a request. Ask for a tweet or Twitter post about a named ForgeCode feature.
- 5Attach the demo video. Attach the video that demonstrates the feature so the post can refer to it implicitly.
- 6Review the draft. Read the 2-3 sentence draft, check the facts, and ask for tweaks if needed.
What is an agent skill, and what does this one do?
An agent skill is a folder of instructions and optional files that an AI agent loads when a task matches the skill's description. This skill, post-forge-feature, is triggered when you ask for a tweet, a Twitter post, or a promotion of a ForgeCode feature on social media.
When it runs, the agent first reads the relevant source code, docs, or changelog to work out what the feature does, when a developer would use it, and what problem it removes. It then drafts 2-3 sentences that follow the style guide and shows you the draft, asking whether you want changes before it is finalized.
- Reads the feature's code, docs, or changelog before writing anything
- Keeps the post to 2-3 sentences, which fits about 280 characters
- Uses the name "ForgeCode" and never "Forge" alone
- Avoids em dashes, filler phrases, and hype words
- Ends with an approved hashtag line
- Assumes a video is attached and does not describe it
Install the post-forge-feature skill
Download the skill as a ZIP from this page. Unzip it so the skill folder ends up in one of these locations:
For a personal install that works across your projects, unzip it into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder.
If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload
Trigger the skill with a natural request
You do not need a special command. Ask for a tweet or social post about a specific ForgeCode feature in plain words, and mention the feature by name so the agent knows what to read. The skill's description lists the trigger phrases it responds to: write a tweet, create a Twitter post, or promote a ForgeCode feature on social media.
Because the skill assumes a video is attached, attach your demo video to the conversation when you make the request.
- "Write a tweet about the new task context feature in ForgeCode."
- "Create a Twitter post promoting the file watcher in ForgeCode. The demo video is attached."
- "Draft a social post for our ForgeCode changelog entry on workflows."
Review and approve the draft
The agent will show you a draft and ask if you want tweaks. Check three things before you publish: that the feature is described accurately against the code or changelog, that the post opens with the developer benefit rather than the feature name, and that the hashtags match the approved set in the style guide.
Ask for specific edits in plain terms, such as shortening the post or changing the tone. The agent will revise within the same constraints.
- Check the facts against the changelog or docs
- Confirm the post does not refer to the video's contents
- Confirm the hashtag line is present at the end
What the skill needs and its safety notes
The skill lists no required tools or packages. It does not run scripts, and it does not use the network. Its files are SKILL.md and references/style-guide.md, which you can open and read before installing.
Because the skill reads source code and docs through your agent's tools, it can only see what your agent has access to in the project you are working in. Review the draft yourself, since the agent may still describe a feature inaccurately.
- No required dependencies are listed
- Runs scripts: no
- Uses network: no
- Files: SKILL.md and references/style-guide.md
What people use it for
- Announcing a new ForgeCode release feature alongside its demo video
- Writing a consistent tone for each feature post across a community team
- Turning a changelog entry into a short social post for developers
- Drafting a first version that a maintainer edits before publishing
Frequently asked questions
How do I install the post-forge-feature skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload it in the Claude apps under Settings, then Capabilities, then Skills.
Does the post-forge-feature skill require anything else to run?
The skill lists no required dependencies. It does not run scripts and does not use the network, according to its listing.
Is the post-forge-feature skill free?
The source material provided for this page does not state pricing or licence terms beyond the Apache-2.0 licence listed for the ForgeCode repository. Check the repository's licence file for details.
Can I use this skill for posts without a video?
It is not recommended. The skill assumes a demo video is attached and may refer to it even when none exists, so it is not useful for general copy.
Can I use this skill for blog posts or documentation?
No. Output is capped at 2-3 sentences, so it is designed for short social posts, not long-form blog posts or documentation.
Does this skill work for products other than ForgeCode?
No. The naming and hashtag rules are specific to ForgeCode, so it is not suitable for other products.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits maintainers and community staff who publish a short demo video with each ForgeCode feature and want a consistent, developer-friendly tone. Skip it if you need long-form content, posts without a video, or copy for a product other than ForgeCode.
Download the skill