Loading...
Loading...
Found 847 Skills
Extract BUAA classroom replay artifacts from `livingroom` or `coursedetail` URLs by reusing a local Chromium login session. Use when Codex needs replay metadata, course-transcript files, optional PPT auxiliary artifacts, replay-ready lesson lists, or a standalone semantic rebuild packet / final lesson note.
Longbridge community topics for stocks — list topics by symbol, search by keyword, view topic detail and replies, browse your own topics, and post new topics or replies. Read operations require no login; posting requires login. Triggers: "社区话题", "股票讨论", "社区讨论", "发帖", "话题", "评论", "社群", "市场看法", "帖子", "社區話題", "股票討論", "社區討論", "發帖", "話題", "評論", "社群", "社區看法", "community topic", "stock discussion", "community post", "market opinion", "post comment", "TSLA community", "AAPL discussion", "我的话题", "我的帖子", "发布话题", "回复话题", "發布話題", "回覆話題", "发表看法", "community reply".
Generate self-contained, beautiful HTML documents that replace walls of markdown. Use this skill whenever the user asks for a report, comparison, explainer, slide deck, diagram, post-mortem, status update, code walkthrough, design system showcase, prototype, or interactive editor — or mentions creating HTML outputs, dashboards, visual documentation, or "instead of markdown". Covers 10 battle-tested patterns: comparison, walkthrough, review, design-system, prototyping, diagram, deck, explainer, report, and editor.
One-time setup skill that builds a personalized inbox triage knowledge base via interactive interview. Interviews the user about their email patterns, business context, reply style, and priorities using grill-me discipline (one question at a time, forcing format where possible, dependency-ordered, each question explains why I'm asking), then generates the knowledge base files that power the companion 'inbox-triage' skill. Run this once before using inbox-triage for the first time. Re-run when business, pricing, or priorities change significantly. Triggers: 'set up my inbox', 'configure inbox triage', 'set up my email system', 'configure email triage', 'build my email knowledge base', 'initialize email management', 'set up inbox triage', 'onboard email triage', or any variation where someone wants to get the email triage system running for the first time.
Configure an AI agent to send OpenTelemetry traces to Coval. Use when a user wants to add Coval tracing, instrument an agent for simulations or conversation monitoring, make traces show up in Coval, handle SIP/PSTN/WebSocket trace correlation, or replace the one-command wizard with a security-reviewable manual setup.
Used when an Agent needs to control OpenTeam via the local openteamcli: create AI group chats, add temporary roles, publish tasks, wait for replies, read results, or continue existing group chats.
Respond to online reviews. Use when: drafting replies for Google, Yelp, G2, or building review response templates.
Verify a research claim or academic citation by tracing it through publication → methodology → raw data → independent replication. Routes through perplexity-research for the actual web lookup, then formats results as a citation-checked brain page. Use when a book/article/conversation cites a study and you want to confirm the claim is real, replicated, and accurately characterized.
Use this skill when working with Xquik's X Twitter Scraper API for tweet search, user lookup, follower extraction, media workflows, monitors, webhooks, MCP tools, SDKs, and confirmation-gated X account actions. Triggers on Twitter API alternatives, X API automation, scrape tweets, profile tweets, follower export, send tweets, post replies, DMs, and X/Twitter data pipelines.
Workload-aware architecture design for Apache Doris. MUST USE when designing data architectures, choosing between data models, planning ingestion strategies, sizing clusters, or translating business requirements into Apache Doris system designs. Complements doris-best-practices with decision frameworks and sizing-first workflow. Use when user describes a workload involving: IoT, sensor data, telemetry, real-time analytics, dashboard, log analysis, log search, CDC sync, time-series, device monitoring, point query service, ad-hoc analytics, lakehouse federation, ETL/ELT pipeline, report analytics, clickstream, user behavior, observability, metrics, fleet tracking, or any OLAP workload requiring table design from scratch. Also triggers on prompts like: "design a table for...", "how should I store...", "build an architecture for...", "we have X devices sending data every Y seconds", "recommend a cluster size for...", "what data model should I use for...", "we need to ingest X GB/day", "migrate from MySQL/PostgreSQL to Apache Doris". Also use for legacy analytics/search/serving stack consolidation prompts even when Apache Doris is not named explicitly, including replacing or migrating from Impala, Kudu, Elasticsearch/ES, Greenplum, Presto, HBase, Hive, Hadoop, Redis, or Lambda-style multi-engine data platforms.
Install a per-turn canary signal (e.g. starting every reply with the user's name and a turn counter) so silent context degradation becomes visible the moment it happens, and run a recovery protocol when the canary trips. Use when the user mentions a "canary", "context canary", or "canary check", asks to detect context rot / compaction / drift, says "you stopped using my name" or "did you lose context", asks "how degraded is your context", or wants an early-warning system for long agent sessions.
Your agent goes blind after send. Sync Smartlead, Instantly, HeyReach, and 5 more sequencers into one local SQLite database your agent can query directly. Every reply, click, bounce, and booking lands on your machine. No CSV exports, no merged sheets, no API round trips.