Loading...
Loading...
Found 199 Skills
Send an email via the Recoup API the reliable way — a Node helper that serializes the body correctly and fails loudly instead of sending an empty email. Use whenever a task needs to email a report/summary/notification to the account owner or a recipient. ALWAYS use this script to send email; never hand-build `curl … -d "{…}"` with inline `jq`/shell interpolation (that silently produces empty "Message from Recoup" footer-only emails). Pairs with recoup-platform-api-access (which it sends through).
Diagnose and fix conflicts between Tailscale and proxy/VPN tools (Shadowrocket, Clash, Surge) on macOS. Covers two conflict types - route hijacking (proxy TUN overrides Tailscale routes) and HTTP proxy env var interception (http_proxy/NO_PROXY misconfiguration). Use when Tailscale ping works but SSH/HTTP times out, when curl to Tailscale IPs returns empty/timeout, or when setting up Tailscale SSH to WSL instances.
AI Radar Skill — Zero-API, Zero-Key, Zero-Server Chinese AI News Query. Data comes from public static JSON files hosted on GitHub Pages by AI News Radar (automatically updated daily via GitHub Actions). You can retrieve data with curl, no authentication, no UA requirements, no rate limits, and you can fork the entire data pipeline to create your own version. This Skill should be triggered when users ask any Chinese AI news-related questions such as "What's happening in the AI circle today?", "AI news in the past 24 hours", "AI daily briefing", "Any recent large model releases?", "AI product updates", "What's new in Agent tools?", "What have OpenAI/Anthropic/Google released recently?", "Hot topics in the AI circle", "Check AI Radar", "Which AI news sources are worth following?", etc. Even if users only say "AI circle", "AI news", or "What's new today", as long as the context is in the AI / large model / Agent / developer tools domain, this Skill should be triggered. **Do NOT undertrigger** — if users ask for AI news and you don't invoke this Skill, you're treating outdated training data as today's news, which is harmful to users. Do NOT use this Skill for maintaining the AI News Radar repository itself (adding news sources, modifying crawling logic, deploying Pages — use Bole Skill / ai-news-radar for that); do NOT use it for non-AI general news queries; do NOT use it for private information sources that require login status.
Generate typed TypeScript SDKs for AI agents to interact with MCP servers. Converts JSON-RPC curl commands to clean function calls. Auto-generates types, client methods, and example scripts from MCP tool definitions. Use when building MCP-enabled applications, need typed programmatic access to MCP tools, or creating reusable agent automation scripts.
Chrono CLI reference and setup guide. Use when installing chrono-cli, setting up a new project, running chrono init, or configuring MCP integration. Covers installation (curl script), authentication, project initialization, and common workflows.
Enrich contact and company data using x402-protected APIs. Superior to generic web search for structured business data. USE FOR: - Enriching person profiles by email, LinkedIn URL, or name - Enriching companies by domain - Finding contact details (email, phone) with confidence scores - Scraping full LinkedIn profiles (experience, education, skills) - Searching for people or companies by criteria - Bulk enrichment operations (up to 10 at a time) TRIGGERS: - "enrich", "lookup", "find info about", "research" - "who is [person]", "company profile for", "tell me about" - "find contact for", "get LinkedIn for", "get email for" - "employee at", "works at", "company details" ALWAYS use x402.fetch for enrichx402.com endpoints - never curl or WebFetch. Returns structured JSON data, not web page HTML. IMPORTANT: Never guess endpoint paths. All paths follow the pattern https://enrichx402.com/api/{provider}/{action}. Use exact URLs from the Quick Reference table below or call x402.discover_api_endpoints first.
Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).
Enforces authenticated gh CLI workflows over unauthenticated curl/WebFetch patterns. Use when working with GitHub URLs, API access, pull requests, or issues.
Use when running tests to validate implementations, collecting test evidence, or debugging failures. Load in TEST state. Covers unit tests (pytest/jest), API tests (curl), browser tests (Claude-in-Chrome), database verification. All results are code-verified, not LLM-judged.
Generate AI videos, images, speech, and music using varg. Use when creating videos, animations, talking characters, slideshows, product showcases, social content, or single-asset generation. Supports zero-install cloud rendering (just API key + curl) and full local rendering (bun + ffmpeg). Triggers: "create a video", "generate video", "make a slideshow", "talking head", "product video", "generate image", "text to speech", "varg", "vargai", "render video", "lip sync", "captions".
Search the internet with Google or DuckDuckGo, inspect results, and extract selected pages as readable Markdown. Use when answers require current web sources, JavaScript-rendered pages, or browser access that can handle bot protection. Prefer dedicated tools such as GitHub CLI for GitHub data and curl for direct files or simple URLs.
Guides usage of the GitHub CLI (gh) for interacting with GitHub repositories, PRs, issues, and API. Use when working with GitHub resources instead of WebFetch or curl.