Loading...
Loading...
Found 977 Skills
Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.
Central skill registry and management system. Auto-loaded on every session. Auto-loaded on startup to provide skill discovery and invocation capabilities. Commands: - /skills - List all available skills with descriptions - /skill <name> - Load and activate a specific skill - /skill reload - Refresh skill registry - /skill help <name> - Show detailed help for a skill Capabilities: Auto-discovery of all skills in workspace, unified skill invocation via /skill command, skill registry with metadata and descriptions, version tracking and dependency management.
Pitch-book company profile page via Longbridge — generates a professional company profile for trading materials and client presentations: positioning quadrant (market position / growth), business highlights, key financial matrix (revenue / EBITDA / net income / EPS / PE / EV), price trend description, major shareholders and management, recent catalysts. More presentation-focused and investment-banking oriented than longbridge-company-tearsheet. Triggers: "公司画像", "公司简介页", "投行公司页", "公司展示", "公司描述", "公司介绍页", "公司信息页", "公司畫像", "公司簡介頁", "投行公司頁", "pitch book", "company profile page", "company profile", "company description", "investor profile", "company slide", "company overview page", "pitch book company page".
Initiating-coverage report framework — five-step workflow to generate an institutional-grade coverage initiation report: ① company overview ② industry positioning ③ financial modelling ④ valuation analysis ⑤ investment conclusion. Covers business description, competitive advantages, financial health, valuation multiples, price target, and risk factors. Triggers: "首次覆盖", "初始覆盖", "覆盖报告", "研报框架", "投资报告", "建立覆盖", "首次評級", "初始覆蓋", "覆蓋報告", "建立覆蓋", "initiate coverage", "coverage initiation", "first coverage", "equity research report", "investment report", "initiating coverage", "research initiation", "NVDA initiate coverage".
You are a social media content strategist for Instagram and Facebook. Use this skill when the user wants to plan, write, or optimize content for Instagram or Facebook. Activate when the user mentions "Instagram post," "Facebook post," "Reel script," "Reel idea," "Instagram Stories," "Facebook Story," "carousel plan," "content calendar," "weekly content plan," "social media strategy," "content pillars," "funnel stage content," "repurpose this post," "write a caption," "content for my business," "single image post," "quote post," "behind the scenes," "batch content," "launch story sequence," "Facebook group post," "Facebook Shop," "content performance," "rewrite this caption," "optimize for saves," "optimize for shares," "social content plan," "content for a coach," "content for ecommerce," or "platform-specific content." Covers all Instagram formats (single image, Reels, carousels, Stories) and all Facebook formats (story-driven updates, ads, group posts, shop descriptions). Outputs include structured content tables, full post scripts, captions, repurposing plans, and visual direction.
Collect pins from Pinterest — title, description, image, saves, source. Use when the user wants to collect pin details for research or inspiration.
Generate AI videos from text prompts using multiple provider gateways. Use when: (1) Generating videos from text descriptions, (2) Creating AI-generated video clips for content production, (3) Image-to-video generation with a reference image, (4) Choosing between video generation providers (VEO, Kling, Sora, Runway, Seedance, MiniMax, Gemini Omni). Supports gateways: HeyGen API, fal.ai API, Kling official direct API, and the Gemini API (Gemini Omni Flash).
Embed screenshots, images, diagrams, GIFs, and screen recordings in GitHub PRs and issues — or stage them ahead of a PR, collect them into one attachments comment, or get a durable public link to share a visual with a person. Use this whenever a visual needs to end up in a PR description, issue body, or PR/issue comment, in front of a teammate, or saved for a PR that doesn't exist yet. Triggers include "attach a screenshot to the PR", "add a before/after to the issue", "include a screenshot of …", "share a GIF of the flow", "record the bug and put it in the issue", "get me a link I can paste in Slack", "stage screenshots for the PR", "attach this when I open the PR", "save this for the PR", "collect the PR's media", or having just captured or changed something visual that a shot would make clearer — even mid-task, before a PR exists. Also applies when an agent has no local filesystem and is uploading via the hosted MCP (agents.uploads.sh). Reach for this instead of drag-and-drop or github.com/user-attachments (agents can't upload there) and instead of hand-rolling cloud-storage uploads. Capture the visual with whatever browser or screenshot tooling you have; this skill covers hosting and embedding it.
Analyze a task specification, review the codebase, and output a detailed assessment and success criteria. Use when user provides a new ticket or description to understand scope, risks, and definition of done before implementation.
Writes and edits prose in a plain and boring style: simple everyday words, complete sentences, no dashes, no jargon, and no analogies. Use when drafting or revising documents, Notion pages, reports, summaries, READMEs, emails, slides, commit messages, or PR descriptions, or when the user asks to simplify, clean up, tighten, reword, or make writing clearer. Use when the user invokes /plain-writing deslopify or asks to deslopify an agent response. Do not apply to code, only to the words around it.
Infer and audit skill tags from names, descriptions, and catalog authoring rows. Use when organizing catalog taxonomies. NOT for live catalog index edits.
Write and maintain a CHANGELOG that records every completed code change without becoming a commit dump. Use after any code change in a project that has a changelog, when setting one up, when preparing a release, or when the user asks why something was built this way. Keep mechanical entries brief; preserve reasons and rejected alternatives for non-obvious decisions. Do not use for commit messages, PR descriptions, or user-facing release notes.