Loading...
Loading...
Found 12,679 Skills
AI HOT (aihot.virxact.com) Chinese AI News Query Skill. Trigger this Skill when users ask any Chinese AI information queries such as "What's happening in the AI circle today", "AI Daily", "AI HOT", "AI News", "AI Hot Topics", "Latest AI Updates", "What have OpenAI/Anthropic/Google released recently", "AI hot today", "AI news today", "Check AI industry trends", "What large models are released today", "AI circle updates from yesterday", "Check selected items", "AI HOT Selected", "AI papers from the past week", "AI model releases", "AI product launches", "AI industry dynamics", "AI tips and insights". Even if users only say "AI circle", "AI news", "AI Daily", or just ask "What happened today" with context related to AI / large models / LLM / startup fields, this Skill should be triggered. The Skill directly pulls data via curl from public REST APIs and organizes it into Chinese markdown briefings, with no need for users to configure any API Key or MCP server. **Do NOT undertrigger**——If users ask for AI news and you don't invoke this Skill, you are treating outdated training data as today's news, which is harmful to users.
Process routed inbox or directive messages from probe next and respond with concrete updates before returning to probe next.
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
Persistent memory system for Claude Code. Two-layer architecture (hot cache + knowledge wiki), safety hooks, /close-day end-of-day synthesis. Zero external dependencies.
6 pharmaceutical research skills. Trigger: drug discovery, pharmacology, clinical trial design, regulatory filing. Design: end-to-end pipeline from target identification to clinical trials.
Use when someone asks to generate ad copy, write headlines, create copy suggestions, or draft marketing text — without generating a design. Also use when the user mentions 'copy suggestions,' 'headline ideas,' 'ad copy,' 'write copy for my ad,' 'content for my design,' 'text for my banner,' 'offer text,' 'bullet points for my ad,' 'CTA text,' or 'what should my ad say.' Generates structured copy variations using content expert instructions — no API call needed. Default is 2 variations; user can request more (e.g., 3–4 for A/B testing). Copy is presented in readable format for user review and edit, with JSON output for use in generate-design. For generating designs (which now includes copy generation as step 1), see generate-design.
The always-on protocol for the loam skill namespace. Use at session start and whenever a loam task appears. Routes goals and other loam work, explains the memory model (memory = umbrella; wiki, guidance, and checkpoints are substrates), and lists cross-cutting rules. This is a routing/meta skill — delegate to a specific loam skill rather than performing work itself.
Advanced om-auto-create-pr for long, multi-step spec implementations needing resumability and strict step tracking — run folder (PLAN/HANDOFF/NOTIFY), one lean commit per Step, checkpoint verification every ~5 Steps with integration tests and UI screenshots, full gate at completion, ready labeled PR. Resumable via om-auto-continue-pr-loop. Use plain om-auto-create-pr for small fixes.
Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.
Implement a task with automated LLM-as-Judge verification for critical steps
Systematically fix all failing tests after business logic changes or refactoring
Evaluate solutions through multi-round debate between independent judges until consensus