Loading...
Loading...
Found 727 Skills
Use this skill as foundation for git workflows. Use when verifying workspace state before other git operations, checking staged changes, preflight checks before commits or PRs. Do not use when full commit workflow - use commit-messages instead. DO NOT use when: full PR preparation - use pr-prep.
Use this skill when optimizing for AI-powered search engines and generative search results - Google AI Overviews, ChatGPT Search (SearchGPT), Perplexity, Microsoft Copilot Search, and other LLM-powered answer engines. Covers Generative Engine Optimization (GEO), citation signals for AI search, entity authority, LLMs.txt specification, and LLM-friendliness patterns based on Princeton GEO research. Triggers on visibility in AI search, getting cited by LLMs, or adapting SEO for the AI search era.
Use this skill when performing a comprehensive SEO audit - technical audit, on-page audit, content audit, off-page audit, and AEO/GEO readiness assessment. Provides a structured scorecard with 30-40 checks rated PASS/FAIL/WARN across all SEO categories, prioritized recommendations, and links to specialized skills for deep fixes. This is the master audit skill that orchestrates all other SEO skills.
Security vetting for AI agent skills. Use before installing any skill from ClawHub, GitHub, or other sources.
The basics of how to program GPUs using Mojo. Use this skill in addition to mojo-syntax when writing Mojo code that targets GPUs or other accelerators. Use targeting code to NVIDIA, AMD, Apple silicon GPUs, or others. Use this skill to overcome misconceptions about how Mojo GPU code is written.
Help to write Mojo code using current syntax and conventions. Always use this skill when writing any Mojo code, including when other Mojo-specific skills (e.g., mojo-gpu-fundamentals) also apply. Use when writing Mojo code, translating projects to Mojo, or otherwise generating Mojo. Use this skill to overcome misconceptions with how Mojo is written.
Is SM buying this token on one chain but selling on another? Detect capital rotation.
When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer profile," "ICP," or "ideal customer profile."
Comprehensive guide for AntV L7 geospatial visualization library. Use when users need to: (1) Create interactive maps with WebGL rendering (2) Visualize geographic data (points, lines, polygons, heatmaps) (3) Build location-based data dashboards (4) Add map layers, interactions, or animations (5) Process and display GeoJSON, CSV, or other spatial data (6) Integrate maps with AMap (GaodeMap), Mapbox, Maplibre, or standalone L7 Map (7) Optimize performance for large-scale geographic datasets
Build apps that integrate with external services via Membrane. Use when the user wants to add integrations to their product — let their customers connect to Slack, HubSpot, Salesforce, GitHub, Google Sheets, Jira, or any other app, execute actions, sync data, or handle webhooks. Covers backend token generation, frontend connection UI, running actions, data collections, and AI agent tooling.
DingTalk Address Book and Contact Query. Use this skill when the user mentions terms like "DingTalk address book", "find employee", "search user", "check user info", "get user details", "user phone number", "employee name", "employee ID", "check department", "search department", "department members", "department list", "department details", "sub-department", "parent department", "department path", "total number of employees", "address book search", "userId to unionId", "unionId to userId", "dingtalk contact", "dingtalk directory", "find user", "get user info", "department members". Supported operations: search users/departments by keyword, get complete user information (name/phone/employee ID/department/position/unionId), get department member list, get department tree structure, query user's department path, count total number of employees, and all other address book operations.
Use Antithesis documentation efficiently for product, workflow, and integration questions. Prefer the snouty docs CLI when available, and otherwise request markdown versions of documentation pages directly.