Home / huytieu / cog-second-brain · GitHub

release-comms SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

release-comms from huytieu/cog-second-brain is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add huytieu/cog-second-brain/release-comms@git:20261023.65f43f1

Pins git:20261023.65f43f1 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: huytieu/cog-second-brain
Path: skills/release-comms/SKILL.md
Versions recorded: 1
Latest version: git:20261023.65f43f1, committed Oct 23, 2026
Size: 7,987 bytes
Repository stars: 1,350
License: MIT

Release communication pipeline for your product: turn a deployment runsheet and a GitHub milestone into a customer-facing release note with real screenshots and videos, docs updates (including retrofits of articles the release makes stale), a Slack announcement draft, and a lightweight marketing package. Use when you say "cover today's release", "write the release note", or "/release-comms".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# release-comms: release note, docs, announcement and marketing pipeline

**Lane: `full`.** It mutates external state (Slack posts, docs PR, wiki pages), so every post and PR is drafted first and gated on the user's explicit approval. See the `closed-loop` skill.

## Configuration

Fill these in once (`kit.toml`, `.env` or arguments). Placeholders below are examples.

| Setting | Meaning | Example |
|---|---|---|
| `PRODUCT_REPO` | Repo that holds the release milestone | `your-org/your-product` |
| `MILESTONE_PATTERN` | Milestone naming | `Release YYYY-MM-DD` |
| `TEAM_LABEL` | Label that filters the milestone to your team | `team:platform` |
| `RUNSHEET_SOURCE` | Where the deployment runsheet lives | a wiki page, a doc, or a Slack thread |
| `RELEASE_DIR` | Working folder per release | `comms/release-notes/<date>/` |
| `DOCS_REPO` | Local path of the docs repo | `../your-docs` |
| `RELEASE_NOTES_FILE` | Running release-notes page in the docs repo | `docs/release-notes.md` |
| `ANNOUNCE_CHANNEL` | Slack channel for the internal announcement | `#product-releases` |
| `MARKETING_CHANNEL` | Slack channel for the marketing package | `#marketing` |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add huytieu/cog-second-brain/release-comms@sha256:ac7222d6bbd262a1

The line at the top of this page pins the label git:20261023.65f43f1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_zp3m5qefjbwkkwjk.svg)](https://markdownregistry.com/a/art_zp3m5qefjbwkkwjk)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 23, 2026.

version	committed	commit	size	audit
git:20261023.65f43f1 latest	2026-10-23	65f43f1	7,987 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7987 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

GitHub

huytieu/cog-second-brain · 1,350 stars · license MIT · pushed 2026-10-23 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_zp3m5qefjbwkkwjk
GET https://markdownregistry.com/api/v1/resolve?ref=huytieu/cog-second-brain/release-comms
GET https://markdownregistry.com/api/v1/blob/ac7222d6bbd262a1a539dd289b616b76db1ea3650cfa77b7903c6eb5e5deb711

Your AI assistant 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.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from huytieu/cog-second-brain

auto-research SKILL.md skill

huytieu/cog-second-brain · .agents/skills/auto-research/SKILL.md · Deep strategic research engine — decomposes questions into parallel research threads, spawns multiple agents, and…