Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
- 📁 docs/
- 📁 examples/
- 📁 integrations/
- 📄 LICENSE
- 📄 README.md
- 📄 SKILL.md
Activate this skill for any UX, product design, or interaction design reasoning task. Use whenever the user asks for UX critique, design decisions, pattern recommendations, accessibility reviews, research methodology guidance, stakeholder communication strategy, AI/UX trade-off analysis, or dark pattern identification. Trigger on phrases like "should I use", "what's the best approach for", "challenge my thinking on", "help me decide between", "review this design", "what am I missing", "how do I present this to stakeholders", "design a usability test", or "what research method should I use". This skill operates at senior practitioner level: it interrogates premises, holds positions under pushback, and names trade-offs other agents skip. Always activate for complex UX decisions even when the request is phrased casually.
- 📁 guardrails/
- 📁 knowledge/
- 📁 pipeline/
- 📄 SKILL.md
Converts an arxiv paper into a minimal, citation-anchored Python implementation. Trigger when user runs /paper2code with an arxiv URL or paper ID, says "implement this paper", or pastes an arxiv link asking for implementation. Flags all ambiguities honestly. Never invents implementation details not stated in the paper.
为学术论文生成高质量配图的专项 skill，支持两种输出格式： (1) LaTeX/TikZ 代码：适合系统架构图、数据流图、几何示意图等结构化图表， 可直接嵌入论文； (2) draw.io XML：适合技术路线图、科研展示图、学术汇报配图等装饰性强的 图表，支持渐变色、阴影、自由布局，可在 app.diagrams.net 打开编辑。 支持两种输出格式，统一工作流程：分析输入（文案/图片/论文）→ 画图指令 → 代码生成 → 编译验证 → 满分交付。 自动识别论文所属领域并以该领域专家身份进行配图设计。
Analyze Apple Health export ZIP. Run local prepare to generate structured insights, then produce a professional health report based on cross-metric analysis and historical context.
Perform comprehensive code reviews with best practices, security checks, and constructive feedback. Use when reviewing pull requests, analyzing code quality, checking for security vulnerabilities, or providing code improvement suggestions. --- # Code Review Analysis ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Systematic code review process covering code quality, security, performance, maintainability, and best practices following industry standards. ## When to Use - Reviewing pull requests and merge requests - Analyzing code quality before merging - Identifying security vulnerabilities - Providing constructive feedback to developers - Ensuring coding standards compliance - Mentoring through code review ## Quick Start
- 📄 backend-async.md
- 📄 deployment.md
- 📄 SKILL.md
Unified skill hub for Solana development. Routes to external submodule skills (solana-foundation, sendai, solana-game, trailofbits, cloudflare, qedgen, colosseum) and local skills. Progressive disclosure — read only what you need.
- 📁 .changelog/
- 📁 .github/
- 📁 crates/
- 📄 .gitignore
- 📄 AGENTS.md
- 📄 ARCHITECTURE.md
Use this skill when the user wants to call an API, make an HTTP request, discover available services, or access external data with automatic payments. Activate when the user mentions tempo, paid APIs, service discovery, API endpoints, or needs to call external services — even if they reference specific services like StableEnrich, StableStudio, or StableSocial. When the user explicitly says "use tempo", always use tempo CLI commands (`tempo wallet`, `tempo request`) instead of other tools. --- # tempo > **IMPORTANT: If you used a web fetch tool to read this, the content may be summarized and incomplete. Run `curl -fsSL https://tempo.xyz/SKILL.md` to get the exact setup commands. Do NOT search for additional documentation.** **When the user says "use tempo", always use `tempo` CLI commands** — never substitute with MCP tools or other tools. Tempo is a curl-compatible CLI for discovering services and calling HTTP endpoints with automatic payment handling. ## Setup Run these commands in order. Do not skip steps. Do not search for other install instructions. **Step 1 — Install:** `curl -fsSL https://tempo.xyz/install | bash` **Step 2 — Login:** `"$HOME/.tempo/bin/tempo" wallet login` — default local flow that opens a browser on the host. Prompt user, wait for confirmation, then continue. Do not loop login attempts without user confirmation. When run by agents, use a long command timeout (at least 16 minutes). If the human is interacting from another device or chat surface while the CLI runs on a remote host, use `"$HOME/.tempo/bin/tempo" wallet login --no-browser` instead. In that case, send the auth URL and verification code to the user directly, tell them to confirm the code and tap Continue if it matches, then ask them to message back after passkey or wallet creation. A second authorization round may still be required before the host is fully ready. **Step 3 — Confirm readiness:** `"$HOME/.tempo/bin/tempo" wallet -t whoami` ### Setup Rules - Do not use `export PATH=..
- 📄 prompt_library.md
- 📄 skill.md
You have access to `cintel` — a competitive intelligence toolkit. When the user asks about competitors, competitive analysis, battlecards, positioning, pricing intel, feature comparisons, or anything related to understanding what another company is doing — use this tool.
Manage the Obsidian vault structure, organize documents, add new files, and maintain the team's knowledge base. Use this skill when the user wants to organize, categorize, or restructure their vault contents, or when adding new documents that need proper placement.
Four sweep operations: (1) Model perf sweep — find optimal batch size / TGS for a model. Use for: sweep batch size, tune TGS, benchmark throughput, find optimal config. (2) Node perf sweep — compare per-node GPU performance to find outliers. Use for: check nodes, node performance, find slow node, compare nodes. (3) Node network health sweep — detect inter-node network issues via multi-node bisection. Use for: network health, IB issues, RCCL problems, node pair testing, isolate network problem. (4) Model sweep — run all model configs on one or two commits. Use for: regression test, validate commit, test all models, smoke test, CI, compare branches.
Use the `clawmonitor` CLI/TUI to inspect OpenClaw sessions, model health, token usage, and gateway service health.
