released-cards

Verify instrumentation, create PostHog insights, and close Slack loops for released cards.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulyokota/FeedForward --skill released-cards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: released-cards
Source: https://github.com/paulyokota/FeedForward/tree/main/.claude/skills/released-cards
Command: npx skills add https://github.com/paulyokota/FeedForward --skill released-cards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify instrumentation, build measurement insights, and close the Slack loop for cards that move to Released since the last run. The natural unit is cards released since last processed time. Designed for one-at-a-time depth but fed a batch.

Core Features & Use Cases

  • Verify instrumentation for Released cards to ensure signals exist.
  • Create PostHog insights and aggregate release impact across cards.
  • Manage Slack and Shortcut mutations with gating, checkpoints, and human-in-the-loop validation.

Quick Start

Process the Released cards since the last run to verify instrumentation, generate insights, and close the Slack loop.

Frequently Asked Questions about released-cards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify instrumentation and build measurement insights for released cards?

You can verify instrumentation by processing cards moved to Released since the last run, checking that signals exist, and using PostHog to build measurement insights that aggregate release impact.

How do I close the Slack loop for Shortcut cards that have been released?

Closing the Slack loop for released Shortcut cards is done by automating notifications and updates, using guarded mutations with PreToolUse checks and human-in-the-loop validation to ensure safe delivery.

Can I process released cards in batches instead of one at a time?

Yes, while the process is designed for one-at-a-time depth, it can be fed a batch of cards released since the last run, processing them with gated checkpoints and human-in-the-loop validations.

What is the best way to automate release management notifications across Slack and Shortcut?

Automating release management notifications across Slack and Shortcut requires enforcing gating rules with PreToolUse checks that guard mutations, ensuring all updates pass through human-in-the-loop validation before execution.

Do I need PostHog to generate insights for my released cards?

PostHog is required to build measurement insights and aggregate release impact for cards moved to Released, serving as the analytics platform for verifying that signals exist and measuring outcomes.