post-forge-feature skillA
post-forge-feature is agent-read markdown (skill) from tailcallhq/forgecode: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# 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
1. **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?
2. **Craft the post**: follow the constraints in `references/style-guide.md`.
3. **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
…Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/post-forge-feature@git:20260321.bba73fbmdr add tailcallhq/forgecode/post-forge-feature@sha256:94b54017d7a71dc6Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_shs5ntfk2ozkyk4t)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1493 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_shs5ntfk2ozkyk4t GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/post-forge-feature GET https://markdownregistry.com/api/v1/blob/94b54017d7a71dc6126d5df43acc0cd8dda006f36c1aaf9e2e14dec84c3197d3
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.