Loading...
Loading...
Found 740 Skills
Analyze Taiwan's retail industry including convenience stores, department stores, supermarkets, hypermarkets, and e-commerce with omnichannel trends. Use this skill when the user needs to understand Taiwan's unique retail ecosystem, plan a retail strategy for Taiwan, or evaluate retail channels — even if they say 'how does retail work in Taiwan', 'convenience store strategy', 'Taiwan omnichannel', or 'where should we sell in Taiwan'.
Implement Taiwan's e-invoice (電子發票) system including platform integration, B2B vs B2C formats, carrier consolidation, and tax filing reconciliation. Use this skill when the user needs to set up e-invoicing for a Taiwan business, integrate with the MOF platform, understand carrier codes, or troubleshoot invoice issues — even if they say 'set up e-invoice', 'how does 電子發票 work', 'integrate with 財政部', or 'carrier barcode scanning'.
Analyzes and compares existing skills from any source (skills.sh, GitHub, Claude marketplace, or local files) against a target skill or requirement. Fetches skill content, evaluates it across 10 dimensions, produces a structured comparison table, identifies gaps, and recommends whether to adopt, adapt, or build from scratch. Trigger when: analyze this skill, compare skills, is this skill good enough, what does this skill do, skill evaluation, should I use this skill, skill gap analysis, paste a skills.sh URL, GitHub skill URL, or upload a SKILL.md file for review.
Research and qualify onboarding team referral leads for PostHog. Use this skill when a TAE receives a lead from the onboarding team and needs a full research brief before deciding how to engage. Triggers on 'research this onboarding lead', 'onboarding team referred [company]', 'look into [company] from onboarding', 'qualify this onboarding referral', 'what do we know about [company] from onboarding', or any request to research a company that came through the onboarding pipeline. Also trigger when a TAE pastes a company name and mentions it's from the onboarding team, or says something like 'onboarding sent me [company]', 'got a handoff for [company]', or '[name] from onboarding sent me [company]'. This skill does deep research and qualification, then drafts outreach when the recommendation is to engage.
Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or audit such a base, or initialize a new one. Trigger on phrases like "add this to my wiki", "ingest this paper", "compile this into the knowledge base", "what does my wiki say about X", "lint the wiki", "build a knowledge base from these documents", "research notes", "second brain", "personal knowledge base", or any reference to LLM Wiki / OmegaWiki. Trigger even when the user does not say "wiki" — if they are accumulating sources over time and want them organized, this applies. The skill scales — sharded indexes, atomic pages, YAML frontmatter, and a bundled search script keep the wiki from becoming a context bottleneck at hundreds or thousands of pages.
Planhat platform help — Health Scores, Agentic Automation, Revenue Management, CRM Sync, Enduser Tracking, Projects, NPS, REST API, MCP Server. Use when health scores aren't reflecting churn risk, CRM sync is overwriting fields or not pulling data, metrics take hours to build and formulas keep breaking, automation rules aren't triggering, revenue or license data doesn't match Salesforce, enduser tracking isn't capturing product usage, or the Planhat API returns unexpected errors. Do NOT use for general customer success strategy (use /sales-customer-success) or NPS/CSAT survey methodology (use /sales-customer-feedback).
Download YouTube video transcripts (subtitles/captions) using yt-dlp. Use this skill whenever the user provides a YouTube URL and wants the transcript, asks to "download transcript", "get captions/subtitles", or "transcribe a YouTube video". Also triggers when user needs text content extracted from any YouTube video, even if they don't explicitly say "transcript" (e.g., "what does this video say", "get me the text from this video", "I need the content of this YouTube link").
Conduct a rigorous rapid evidence assessment or systematic-lite literature review for MEL/SRHR questions. Use when Ane asks for "evidence review", "literature review", "evidence synthesis", "REA", "what does the evidence say", "what do we know about", or similar. Produces a structured brief with question framing, method, findings by theme, confidence grading, and implications for programme or evaluation design. Does not invent citations.
Li — Knowledge Manager for Ane's library and MEL Wiki. Use when Ane needs to catalog, retrieve, or reorganize documents in the personal knowledge library, or query/maintain the MEL Wiki. Handles INGEST, QUERY, and LINT operations. Does not answer domain questions — retrieves and organizes knowledge for other agents and Ane.
Create SVG infographics, architecture diagrams, and flowcharts in various styles. Be sure to use this skill whenever the user mentions any of the following scenarios: - Draw flowcharts, architecture diagrams, system diagrams, infographics, schematic diagrams - Use SVG to draw charts, visualize a process or concept - "Help me draw a diagram to explain...", "Generate an architecture diagram", "Draw a schematic" - Visualize text-described systems or processes into diagrams - Want illustrations in specific styles (Anthropic style, dark theme, etc.) Even if the user doesn't explicitly mention "SVG", this skill should be used whenever process/architecture/information visualization is involved.
Root-cause discipline for bugs, test failures, and unexpected behavior. Embedded grill on the hypothesis before writing fix code. Use when encountering any bug, failing test, or behavior that doesn't match expectation.
Navigate the stardust design pipeline — assess project state under `stardust/` and recommend the next design stage. Use when the user wants to check design-pipeline progress, doesn't know which stage to run next, asks a general question about `stardust/` artifacts without naming a specific stage, says `/stardust`, or asks about files under `stardust/` (brand, briefings, wireframes, prototypes) without a clear edit target.