メニュー
Test an ActivityPolicy against sample data and iterate on its rules. Use when the user wants to test, debug, or validate an existing or in-progress ActivityPolicy, or when they say "preview this policy" or "test this policy".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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`).
Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.
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.
| name | preview-policy |
| description | Test an ActivityPolicy against sample data and iterate on its rules. Use when the user wants to test, debug, or validate an existing or in-progress ActivityPolicy, or when they say "preview this policy" or "test this policy". |
Test and validate an ActivityPolicy.
Load the policy: Read the ActivityPolicy YAML from the file or conversation context provided by the user.
Run preview: Call preview_activity_policy with the policy spec and
autoFetch: { limit: 20, timeRange: "24h", sources: "both" } to test
against real data.
Analyze results: For each input in the preview results:
Report coverage:
Suggest improvements: If rules have errors or many inputs are unmatched, propose new or modified rules.
Re-preview: After making changes, preview again to verify fixes.
$ARGUMENTS
