productivity▌

Interprets shorthand, pseudo-code, and natural language descriptions to generate production-quality code. \n \n Assesses collaborator technical expertise (high/medium/low confidence) to determine how much interpretation and correction is needed \n Processes special shorthand notation marked with start-shorthand and end-shorthand boundaries; always removes ()=> lines when implementing \n Applies expert judgment to translate incomplete or imperfect descriptions into robust code, handling typos, te

Export Google Sheets spreadsheets as CSV files for backup or local processing. \n \n Requires gws-sheets and gws-drive skills as prerequisites \n Offers three export approaches: retrieve spreadsheet metadata, export via Drive API with MIME type specification, or read sheet values directly in CSV format \n Supports flexible range selection and sheet targeting for granular control over exported data \n

You're a senior technical analyst and storyteller with expertise in repository archaeology, code pattern analysis, and narrative synthesis. Your mission is to transform raw repository data into compelling technical narratives that reveal the human stories behind the code.

Sanitize user prompts through Google Model Armor safety templates. \n \n Requires a Model Armor template resource name and accepts text input via flag, stdin, or full JSON request body \n Designed for inbound prompt safety; use the companion +sanitize-response command for outbound response filtering \n Integrates with Google Cloud authentication and global flags defined in gws-shared \n

Prerequisite setup for Firebase agent integration: Node.js, CLI authentication, and MCP server installation. \n \n Verifies Node.js v20+ installation and guides setup via nvm or official installers for macOS, Linux, and Windows \n Confirms Firebase CLI availability through npx firebase-tools and authenticates via firebase login with remote environment support \n Directs agent-specific MCP server and skill installation for Gemini CLI, Antigravity, Claude Code, Cursor, GitHub Copilot, and other pl

Socratic mentoring for junior developers through guided questions, never direct answers. \n \n Guides learners through structured questioning rather than solving problems, building autonomy and reasoning skills across fundamentals, debugging, testing, security, and architecture \n Includes the PEAR Loop (Plan, Explore, Analyze, Rewrite) for Copilot-assisted learning and teaches prompt engineering with the CTEX formula for better AI interactions \n Provides progressive clue systems from light gui

Design durable distributed workflows with Temporal, separating orchestration logic from external interactions. \n \n Workflows handle orchestration and decision-making (must be deterministic); activities handle external calls like APIs and databases (must be idempotent) \n Implements saga pattern with compensation for distributed transactions, entity workflows for long-lived state management, and fan-out/fan-in for parallel execution \n Automatic state preservation across failures via event hist

Automatically share Google Drive files with all attendees of a Calendar event. \n \n Requires gws-calendar and gws-drive skills as dependencies \n Retrieves event attendee list from Google Calendar, then grants each attendee reader access to specified Drive files \n Includes verification step to confirm sharing permissions were applied successfully \n

Google Workspace IT administration with security monitoring and configuration capabilities. \n \n Requires three prerequisite skills: gws-gmail, gws-drive, and gws-calendar for full functionality \n Includes standup-report workflow to review pending IT requests and security alerts at the start of each day \n Supports monitoring of suspicious login activity, audit log review, and Drive sharing policy configuration \n Recommends using --dry-run flag before bulk operations and regular permission ve

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