productivity▌

Production-ready skill for building beautiful terminal user interfaces with Go, Bubbletea, and Lipgloss.

Templates and guidance for writing READMEs matched to your project type and audience. \n \n Identifies four project types (Open Source, Personal, Internal, Config) with distinct audience needs and required sections \n Provides a structured three-step process: identify the task (creating, adding, updating, or reviewing), ask task-specific questions, then solicit final feedback \n Includes essential baseline sections for all READMEs: name, description, and usage with examples \n References support

$22

Upscale and enhance image resolution using state-of-the-art AI models.

This skill is based on Quarto CLI v1.9.36 (2026-03-24).

你是一位文字編輯，專門辨識和去除 AI 生成文字的痕跡，使文字聽起來更自然、更有人味。本指南基於維基百科的「AI 寫作特徵」頁面，由 WikiProject AI Cleanup 維護。

Intelligent contract review highlighting risks, key terms, and unusual provisions.

Analyze events through the disciplinary lens of chemistry, applying rigorous chemical principles (atomic theory, bonding, thermodynamics, kinetics), analytical methods (spectroscopy, chromatography, mass spectrometry), synthetic methodologies (organic, inorganic, organometallic synthesis), and subdiscipline frameworks (physical, organic, inorganic, analytical, biochemistry) to understand molecular structure, reaction mechanisms, material properties, and chemical transformations.

Discovers high-value keywords with intent classification, difficulty scoring, and topic clustering for SEO content strategy. \n \n Classifies keywords by search intent (informational, commercial, transactional, navigational) and assigns opportunity scores based on volume, difficulty, and business value \n Integrates with Ahrefs, SEMrush, Google Keyword Planner, and Google Search Console; also accepts manual data input for sites without tool access \n Groups keywords into topic clusters with pill

Converts user coding requests into clear, atomic checklists with minimal back-and-forth. \n \n Scans existing code, docs, and constraints before generating a plan to avoid unnecessary questions \n Produces structured plans with approach, scope boundaries, 6–10 ordered action items, and validation steps \n Uses verb-first, concrete task language (e.g., \"Add X to file Y\") to keep steps logically independent and actionable \n Asks at most 1–2 blocking questions; makes reasonable assumptions for n