pos-releases

Query POS release schedules from CSV data and Slack updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/abhiroopb/synthetic-mind --skill pos-releases
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pos-releases
Source: https://github.com/abhiroopb/synthetic-mind/tree/main/skills/pos-releases
Command: npx skills add https://github.com/abhiroopb/synthetic-mind --skill pos-releases

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires slack-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill consolidates scattered information about Point of Sale (POS) release schedules, making it easy to get clear, up-to-date answers on branch cuts, beta versions, and rollout dates.

Core Features & Use Cases

  • Unified Schedule View: Combines projected dates from CSVs with live status updates from Slack.
  • Release Cadence Understanding: Knows the weekly branch cut cycle and the difference between dry-run and real trains.
  • Platform-Specific Details: Differentiates between iOS and Android release processes and rollout percentages.
  • Use Case: Quickly answer "When is the next iOS branch cut?" or "What is the current rollout status for version 6.45?".

Quick Start

Ask "When is the next branch cut?" to find out the upcoming release date.

Frequently Asked Questions about pos-releases

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

FAQPage Schema
How do I track POS release schedules and branch cuts?

To track POS release schedules and branch cuts, you can query a system that integrates local CSV release data with live Slack channel updates. This approach synthesizes projected dates and actual train status into clear markdown tables for iOS and Android.

Can I get real-time rollout status updates from Slack for iOS and Android releases?

Yes, you can get real-time rollout status updates from Slack for iOS and Android releases. A tracking system queries live Slack channels to capture actual train status, including blockers, delays, and rollout percentages, combining them with projected dates.

How do I find the next branch cut date for a weekly release cycle?

To find the next branch cut date for a weekly release cycle, query your consolidated release schedule data. The system understands the weekly branch cut cadence and differentiates between dry-run and real trains to provide accurate upcoming dates.

Do I need a Slack CLI dependency to track POS beta versions and rollout dates?

Yes, you need a Slack CLI dependency to track POS beta versions and rollout dates. The tracking process requires Python scripts to parse local CSVs and query Slack via the CLI for real-time release information and status updates.

What is the best way to consolidate scattered release train schedules and beta information?

The best way to consolidate scattered release train schedules and beta information is to unify projected dates from local CSV files with live status updates from Slack. This creates a single, up-to-date view of branch cuts, betas, and rollout dates.