routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover
What this skill does
# Routines Use Case Discovery Analyzes this codebase and surfaces actionable Routine candidates across the three trigger types. **Usage**: `/routines-discover` - no arguments needed. Run it in the root of any project. --- ## What Are Routines A Routine is an autonomous Claude Code session running on Anthropic-managed cloud infrastructure, triggered in three ways: | Trigger | How it fires | |---------|-------------| | **Schedule** | Recurring cron cadence (min 1 hour) | | **API** | HTTP POST to a per-routine endpoint with bearer token | | **GitHub events** | Repository events: PR opened/merged, push, issue, workflow run, etc. | Each run clones a fresh copy of the GitHub repository, runs a full Claude Code session with configured MCP connectors (Slack, Linear, GitHub, Google Drive…), and can create branches, open PRs, post messages, and call external APIs. No local machine required. **Daily limits**: Pro 5/day · Max 15/day · Team/Enterprise 25/day. --- ## Instructions ### Step 1: Read the codebase Before generating any output, silently read: - `README.md` or `CLAUDE.md` to understand the project purpose and stack - `package.json`, `Cargo.toml`, `pyproject.toml`, or equivalent for dependencies - `.github/workflows/` to understand existing CI/CD automation - Any monitoring, deploy, or ops configuration you find If MCP connectors are configured in `.claude/settings.json`, note which external services are connected. ### Step 2: Analyze against five dimensions For each dimension, think concretely about this specific project before writing anything. **1. Scheduled maintenance** What recurring work currently requires a human to run manually or remember to do? Think: dependency audits, stale issue/PR triage, test flakiness reports, coverage drift, TODO comment tracking, dead code detection, daily or weekly summaries. **2. Event-driven reactions** What should happen automatically when a PR is opened, merged, or closed, but doesn't today because no one gets to it? Think: review checklists, changelog updates, cross-repo sync, Slack notifications with context, label enforcement, docs updates on API changes. **3. Alert and incident response** What monitoring signals exist? When something breaks, what is the first thing a developer does? Think: correlating an alert with recent commits, triaging a failing build, drafting a postmortem skeleton, routing an error to the right team. **4. Cross-system sync** What drifts today because the sync between two systems is manual? Think: keeping two SDKs in sync, updating a doc site when an API changes, syncing GitHub issues with Linear, keeping a README stats section current. **5. Release and deploy automation** What steps happen before or after a deploy that a human runs by hand? Think: smoke tests, release notes, version bumps, stakeholder notifications, go/no-go summaries. ### Step 3: Output For each use case identified, produce a card in this format: --- **[Name]** · `schedule` / `api` / `github` *Trigger*: [what fires it: cron expression, which event, which external system] *Input*: [what Claude receives: repo state, event payload, alert body] *Output*: [what Claude produces: PR opened, message posted, file updated, issue created] *Value*: [time saved or risk reduced, be specific] *Blockers*: [missing connector, secrets needed, GitHub App required, etc., or "none"] --- Sort cards by **value-to-effort ratio**, highest first. After all cards, add a **Quick Wins** section: the two or three use cases that could be set up in under 15 minutes with the current repo and connector configuration. --- ## Example Output (for reference only, do not copy, analyze the actual project) **Nightly stale PR report** · `schedule` *Trigger*: Every weekday at 8am *Input*: Repo state: all open PRs older than 5 days *Output*: Slack message to #engineering with list of stale PRs, assignee, and last activity *Value*: Saves ~15min of manual triage each morning, reduces PR rot *Blockers*: Requires Slack MCP connector
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.