create▌

Template-based Google Doc creation with automated content population and team sharing. \n \n Requires gws-drive and gws-docs skills; uses Google Workspace APIs for file operations and document editing \n Workflow: copy a template doc, populate it with structured content via the docs API, then grant collaborator access through drive permissions \n Supports markdown-style content insertion and granular permission assignment (writer, editor roles, user/group targeting) \n

Structured Architectural Decision Record generator with AI-optimized formatting and sequential file management. \n \n Generates standardized ADR documents with front matter, context, decision rationale, and consequences organized into positive and negative outcomes \n Requires four inputs (decision title, context, decision, alternatives, stakeholders) with validation to prompt for missing information before generation \n Uses coded bullet-point system (3-4 letter codes + 3-digit numbers) across

Initialize a Google Tasks list and populate it with multiple tasks via command sequence. \n \n Requires the gws-tasks skill to execute task list and task management operations \n Provides step-by-step commands to create a new task list, add tasks with optional notes and due dates, and display results in table format \n Demonstrates task insertion with structured JSON payloads including title, notes, and ISO 8601 due date formatting \n

Create GitHub Issues automatically from implementation plan phases. \n \n Analyzes implementation plan files to identify phases and generates one issue per phase \n Uses feature_request.yml or chore_request.yml templates, with fallback to default issue format \n Checks for existing issues before creation to avoid duplicates, and updates existing issues when needed \n Includes phase details, requirements, and context in issue descriptions with appropriate labels \n

Bulk-create Google Calendar events from spreadsheet rows using a two-step workflow. \n \n Reads event data directly from Google Sheets ranges, extracting summary, start time, end time, and attendee information \n Creates calendar entries via the gws-calendar skill with support for multiple attendees and custom time ranges \n Requires both gws-sheets and gws-calendar skills to be loaded before execution \n

Automatically create GitHub issues for specification requirements not yet implemented in code. \n \n Analyzes specification files to extract all requirements, then checks codebase implementation status for each one \n Searches existing issues to prevent duplicates before creating new feature request issues \n Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria \n Scans related specification files and code patterns to verify whether requi

Create a Google Meet meeting space and email the join link to participants. \n \n Requires two prerequisite skills: gws-meet for space creation and gws-gmail for sending invitations \n Creates an open-access meeting space via the Meet API and extracts the meeting URI from the response \n Automates sharing the join link by composing and sending an email with the meeting details to specified recipients \n

Google Sheets spreadsheet template for expense tracking with automated setup and sharing. \n \n Creates a new spreadsheet with standard expense columns (Date, Category, Description, Amount) and sample entries \n Includes built-in sharing capabilities to grant read or edit access to team members via email \n Requires gws-sheets and gws-drive skills; uses Google Workspace APIs for spreadsheet and file management \n

Generates formal, AI-optimized specifications for GitHub Actions workflows to standardize documentation and enable maintenance. \n \n Produces structured markdown specifications with execution flow diagrams, job dependency matrices, and requirement tables designed for token efficiency \n Covers functional, security, and performance requirements alongside input/output contracts, error handling strategies, and quality gates \n Includes sections for monitoring, compliance, edge cases, and change ma

Design and build isolated, reusable Convex backend components with clear boundaries and app-facing wrappers. \n \n Supports three component shapes: local (single-app), packaged (npm), and hybrid (both), with a decision tree to choose the right fit \n Enforces architectural boundaries: components own their tables and functions, while the app handles authentication, environment access, and client-facing wrappers \n Provides a complete workflow from planning (tables, public API, data flow) through