Loading...
Loading...
Found 9,307 Skills
Use when designing, executing, or facilitating a complete SWOT strategic analysis workflow — especially when the task involves environment scanning (PEST/industry analysis), competitive positioning, S/W/O/T identification and validation, strategy formulation via SO/ST/WO/WT collision, and strategy selection. Trigger on requests such as SWOT analysis, strengths and weaknesses analysis, opportunities and threats analysis, strategy positioning, external environment analysis, competitive strategy, TOWS Matrix, SWOT to strategy, PEST analysis, or any combination of competitive analysis and strategy direction. Also trigger when the user uploads a case, company description, or product brief and asks for strategic analysis or positioning.
Extend Pydantic AI agents with batteries-included capabilities from pydantic-ai-harness — currently Code Mode, which collapses many tool calls into one sandboxed Python execution. Use when the user mentions pydantic-ai-harness, CodeMode, Monty, code mode, or tool sandboxing, when they want an agent to run agent-written Python, or when a Pydantic AI agent would benefit from orchestrating multiple tool calls in a single sandboxed script.
Open or return Logfire project pages, live views, trace links, and Explore pages in the Codex browser without querying telemetry first. Use this skill when the user asks to "open in Logfire", "show in the live view", "open Explore", "open the UI", "show in Codex", "use the browser", "give me a link", or asks for a Logfire GUI/browser/live-view presentation of a project, time range, service, span, trace, log, or filter. If "show" or "view" wording is ambiguous, ask whether the user wants a UI view or query analysis.
Search 78 public scientific, biomedical, materials science, and economic databases via REST APIs. Covers physics/astronomy (NASA, NIST, SDSS, SIMBAD), earth/environment (USGS, NOAA, EPA), chemistry/drugs (PubChem, ChEMBL, DrugBank, FDA, KEGG, ZINC, BindingDB), materials (Materials Project, COD), biology/genomics (Reactome, UniProt, STRING, Ensembl, NCBI Gene, GEO, GTEx, PDB, AlphaFold, InterPro, BioGRID, Gene Ontology, dbSNP, gnomAD, ENCODE, Human Protein Atlas, Human Cell Atlas), disease/clinical (COSMIC, Open Targets, ClinicalTrials.gov, OMIM, ClinVar, GDC/TCGA, cBioPortal, DisGeNET, GWAS Catalog), regulatory (FDA, USPTO, SEC EDGAR), economics/finance (FRED, World Bank, US Treasury), demographics (US Census, Eurostat, WHO). Use when looking up compounds, genes, proteins, pathways, variants, clinical trials, patents, economic indicators, or any public database API query.
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
Crea o actualiza tareas técnicas (TK-XXX) asociadas a una historia de usuario existente. Activar cuando el usuario solicite planificar implementación, descomponer trabajo, definir alcance técnico, estructurar subtareas o documentar especificaciones técnicas sin generar código ni pruebas. Activar también — por defecto — cuando el usuario solo entregue una referencia a una historia (p. ej. «US-004», «planifica US-007», «tareas para esta historia») — en ese caso el propósito es proponer stubs agrupados por unidad de trabajo que cubran los escenarios (SC-XX) y consideren las reglas de negocio (BR-XX) de la US, sin redactar TKs completas.
Automates codebase environment configuration, troubleshooting, and repair. When non-technical users (editors, business personnel, operations staff) get a repository and say things like "it won't run", "how to start", "how to configure the environment", "help me set up the codebase", "initialize the project", "commit code", "what to do about conflicts", it automatically reads ONBOARDING.md, diagnoses environment gaps, fixes dependencies, verifies runnability, and safely completes git operations. It is also used by technical users to quickly standardize the setup process for new repositories (SessionStart hook, PII Guard, history sanitization, project-isolated API keys). This skill is triggered whenever users mention terms like "environment", "configuration", "won't run", "setup", "start", "clone", "how to run", "dependencies", "is it installed", "commit code", "merge conflict", "push failed".
Routes the weakest VCN samples (output of `tao-analyze-gaps-visual-changenet`) into per-augmentation-module subsets — one parquet for k-NN mining, one for AnomalyGen (Cosmos SDG) — based on each module's label eligibility. Use as the immediate next step after DEFT gap analysis in a VCN AOI SDA iteration.
Multi-step video annotation pipeline that turns raw videos into Chain-of-Thought training data — multi-level captions, structured descriptions, and QA pairs (MCQ, binary, open-ended) with reasoning traces, via VLM/LLM distillation. Use when the user wants to "create video training data", "generate video QA datasets", "build CoT reasoning traces from videos", "auto-label videos", or run the video_reasoning_annotation pipeline. Triggers include "video annotation", "video CoT", "video QA", "chain-of-thought", "video captioning pipeline", "video distillation".
Prepend a 4s viral hook + optional designed title to a user's video, then hard-cut into the real clip. An attention-grabbing event erupts into the user's OWN scene; the title is rendered in-scene by Seedance. One MCP call does the whole render. Requires Pika MCP. Triggers: "add a viral hook", "disruption hook on my video", "hook + title on my clip", "viral hook with typography", "scroll-stopper intro".
Use whenever you need to contact someone by email and get their answer back, especially to unblock yourself. PROACTIVELY, and you can usually do this without asking the user first: you are stuck on a tool, library, API, or service and its docs, README, footer, or llms.txt list a help@, support@, dev@, docs@, or agent@ address; you hit a bug or surprising behavior worth reporting to the vendor; you have a question only the product owner or maintainer can answer; you want to ask a vendor's support or dev agent something the same way you would grep their docs. REACTIVELY: the user gave you a mailto link or a contact address, or asked you to email, message, or "ask them" and report back. This sends YOUR outbound message and waits for the threaded reply in one step, so reach for it when you are the one initiating contact (addresses with human side effects like sales@, billing@, or account@ should be surfaced to the user first). No SMTP, no API keys, no mail server. To instead receive mail that a website or service sends to you (signup confirmations, verification codes), use the primitive-inbox skill. Gets a free `*.primitive.email` address via `primitive agent start-agent-signup` if you do not already have one. Part of the Primitive CLI (Primitive, primitivedotdev, primitive.dev; the `primitive` or `prim` command).
Write a structured architecture decision document — an RFC / design doc / technical doc that records *why* a non-trivial technical choice was made, not just what was built. Follows a six-part method: contextualize for a newcomer, state the architecturally-relevant requirements, design components against them with static + dynamic diagrams, weigh every alternative by pros / cons / risks (each risk with impact, probability, mitigation, contingency), record the decision and how it was made, then conclude and communicate. Writes in the language of the request. Reach for it whenever someone is choosing between technical options or documenting one — "write an RFC", "design doc", "architecture decision", "ADR", "tradeoff analysis", "technical documentation of an implementation", "help me decide between X and Y" — even if they never say "RFC". Also fits the retrospective variant: documenting an implementation after the fact (lessons learned, version history).