菜单
Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | gtm-templates |
| description | Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content. |
This skill provides templates for go-to-market communications.
| Template | Purpose |
|---|---|
templates/blog-post.md | Launch blog post |
The changelog and enablement formats are documented inline in this file (see
Changelog Format and Enablement Brief below); they don't have separate
template files. For a community-facing changelog post to the GitHub Discussions
Changelog category, use the changelog-entry skill instead of the release-file
format here.
Why should the reader care? What problem does this solve?
What's the background? Why now?
What's the feature? What can you do with it?
Technical details with code examples.
First steps to try it.
Future direction (without commitments).
Use Keep a Changelog format:
## [1.2.0] - 2024-01-15
### Added
- New feature description
### Changed
- Modified behavior description
### Deprecated
- Feature being phased out
### Removed
- Deleted feature
### Fixed
- Bug fix description
### Security
- Security fix description
Subject: [Feature Name] is now available
[One sentence: what shipped]
[1-2 sentences: why it matters]
[Call to action button]
[Optional: quick start link]
Key messages for customer conversations.
How this compares to alternatives.
Common objections and responses.
Step-by-step demo instructions.
Technical and commercial questions.
Covers GitHub conventions for pull requests, issues, and comments including linking, language style, formatting, and callout syntax. Use when creating PRs, writing issues, or posting comments on Datum Cloud repositories.
Turn raw engineering notes, PR/issue links, commit messages, or a one-line feature description into a changelog entry for Datum Cloud's GitHub Discussions Changelog category: a benefit-led title plus a markdown body, drafted for users and ready to hand off for final capture and publish. Use when someone says "write a changelog entry", "announce this in the changelog", or "post this to the changelog discussions" — this is the community-facing changelog POST, not the Keep a Changelog release file (that lives in `gtm-templates`).
Create a new GitHub release. Verifies CI is green on the release commit and refreshes the third-party NOTICE file before tagging, determines the next version from the latest tag, summarizes merged PRs since the last release, drafts release notes in the established style, and publishes via gh release create. Works for any datum-cloud service repository.
Scan a project repository for strict AGPL-3.0 license compliance across Go, Rust, and JavaScript/React codebases. Use this skill whenever the user asks to check, audit, verify, or enforce AGPL license compliance on a project, repo, or codebase. Triggers on phrases like "check agpl compliance", "audit license headers", "is this project agpl compliant", "scan for license headers", "check my license files", "agpl audit", or any request involving ensuring a project is properly licensed under AGPL. Always use this skill — don't wing AGPL compliance checks from general knowledge.
Covers producing weekly operational reports for the Datum AI Edge. Use when asked for an ops review, traffic report, latency analysis, provisioning report, or edge performance summary. Guides metric queries, anomaly detection, and publishing to datum-cloud/engineering.
Generate a summary of recent cluster activity for handoffs, standups, or status updates. Use when the user asks for a status update, what happened recently, needs a summary for a handoff, or says "catch me up".