update▌

Append deal status updates to a Google Sheets sales tracking spreadsheet. \n \n Requires gws-sheets and gws-drive skills to locate and modify the Sales Pipeline sheet \n Workflow: find the tracking sheet by name, read existing pipeline data, then append new deal rows with date, company, status, amount, quarter, and owner fields \n Integrates with Google Drive and Sheets APIs to maintain a centralized sales pipeline log \n

Automatically regenerates marketplace documentation files from Jinja2 templates and catalog data. \n \n Generates four synchronized documentation files (agents.md, agent-skills.md, plugins.md, usage.md) by reading marketplace.json and plugin metadata \n Provides Python script with command-line options for full generation, selective file output, dry-run mode, and custom path configuration \n Includes pre-built Jinja2 templates with access to comprehensive context: plugins organized by category, i

Maintain accurate llms.txt files that guide LLMs through repository documentation and structure. \n \n Analyzes current repository state against the official llms.txt specification to identify outdated, missing, or incorrect file references \n Organizes essential documentation into logical H2 sections (Documentation, Specifications, Examples, Configuration, Optional) with properly formatted markdown links \n Validates compliance with https://llmstxt.org/ format requirements including H1 header,

Guided workflow for updating Next.js documentation based on code changes and PR reviews. \n \n Analyzes git diffs to identify affected documentation files using a code-to-docs mapping reference \n Provides templates and conventions for scaffolding new feature docs (components, functions, config, guides, file conventions) \n Walks through step-by-step updates to existing documentation with user confirmation before each change \n Includes validation checklist and linting commands to ensure formatt

Update implementation plan files with new requirements for features, refactoring, or infrastructure changes. \n \n Generates machine-readable, deterministic plans structured for autonomous execution by AI agents or humans \n Enforces atomic phases with measurable completion criteria, parallel-executable tasks, and explicit file paths and function names \n Requires strict adherence to a mandatory template with front matter, requirements, implementation phases, alternatives, dependencies, affected

Systematically scan Apple's developer documentation via the Sosumi MCP, identify deprecated SwiftUI APIs and their modern replacements, and update swiftui-expert-skill/references/latest-apis.md.

Generate a daily standup/meeting update through an interactive interview. Never assume tools are configured—ask first.

Automated Azure Verified Module version updates for Bicep files with breaking change detection. \n \n Scans Bicep files to extract AVM module references, queries MCR for latest versions, and applies updates automatically \n Pauses for manual approval when breaking changes, security modifications, or parameter incompatibilities are detected \n Validates all changes with bicep lint and bicep build to ensure compliance before finalizing \n Outputs results in a structured table showing module names,

Interactive daily standup generator that pulls activity from GitHub, Jira, and Claude Code history. \n \n Detects available integrations (GitHub CLI, Jira, Claude Code session history) and asks permission before pulling any data \n Conducts a structured 4-question interview (yesterday's work, today's plan, blockers, discussion topics) with pulled data as context to trigger memory \n Generates clean Markdown updates combining interview responses with tool data, including PR links and ticket summa

Update specification files for AI-ready consumption based on new requirements or code changes. \n \n Modifies existing specification documents in /spec/ directory using structured markdown with YAML front matter \n Ensures specifications are precise, unambiguous, and machine-readable through established formatting standards (headings, lists, tables, code blocks) \n Covers 11 core sections: purpose, definitions, requirements, interfaces, acceptance criteria, testing strategy, rationale, dependenc