Loading...
Loading...
Found 204 Skills
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".
Standing backlog of work only a human can do — env vars, DNS, dashboard config, third-party signups, decisions. Other skills file into it mid-run without halting; `/manual-tasks` walks the open list, doing what it can and asking for the rest. Reads `.claude/conventions.yaml` for the Linear team and evergreen project.
Generate enriched lead lists using Exa Agent. Finds companies matching an ICP, enriches with signals/news/scores, and outputs CSV. Use when generating leads, building prospect lists, finding companies to sell to, doing outbound research, or ICP-based company discovery. Triggers on "leads", "lead gen", "prospect list", "find companies", "ICP", "outbound list".
Rules for handing work to subagents instead of doing it on the main thread. Use when deciding whether to delegate a search, a bulk edit, a documentation lookup or a verification; when writing a delegation prompt; when choosing a model tier; when escalating after a failure; when running agents in parallel; or when a delegated result comes back and you are about to believe it. Covers hard delegation thresholds, the three mandatory prompt elements, the reporting contract, anti-anchoring, parallel-write safety, and why not to ask the user to switch models mid-conversation.
Multi-agent shared blackboard: The current directory is .yomi/boards/<feature>.md, one board per feature, allowing parallel agents/subagents under the same feature to see each other's tasks, progress, and findings. Use when multi-agent collaboration requires peer visibility, sharing progress/findings, wanting to know what peers are doing before starting work, or when terms like "blackboard / board / peer progress" are mentioned. Task assignment/sign-off/state machine/acceptance are handled via task-tickets, not blackboard.
When you want to create, adapt, or update a Claude Code skill in one of your sibling repos (list your own repos in ~/.config/makerskills/skillify/repos.yaml; defaults to makerskills). Routes to the right mode automatically. Modes — CREATE (from-chat / from-video / from-dump / from-scratch) turns a workflow, brief, recording, or fresh idea into a new skill. ADAPT ports an external skill (GitHub URL, agentskills.io, local disk) into your namespace with three-bucket classification (keep/adapt/add) + license check + attribution. UPDATE improves existing skills from learnings with cross-skill propagation, memory-vs-skill triage, and semver discipline. Defers to Anthropic's guidance (compound-engineering:create-agent-skill, compound-engineering:skill-creator, compound-engineering:heal-skill) for schema and best-practice depth. Triggers on "/skillify," "create a skill," "make this a skill," "skill from this chat," "extract a skill from what we've been doing," "adapt this skill," "port this skill," "fork this skill," "borrow this skill," "update X skill," "apply this to the relevant skills," "propagate this learning," "improve [skill]," "fix [skill]," "iterate on [skill]." Part of the -ify trifecta (skillify / toolify / loopify) for extending Claude Code.
Covers creation and maintenance of a custom Bitrix module in /local/modules/<vendor>.<module>/ — CModule class, install/index.php, DoInstall and DoUninstall, install/version.php with $arModuleVersion, registration of events and agents during installation, module options (options.php), generation via make:module. Applied when creating a new module, refining installation/uninstallation, registering event handlers and publishing module options in the Admin Panel. Key terms — CModule, DoInstall, DoUninstall, module manifest, install/index.php, make:module, vendor.module.
Edward de Bono's Concept Fan — climb from the current solution to the concept it serves by asking "what is this a way of doing?", then fan out alternative concepts and concrete implementations for each. Use when the current solution might be answering the wrong question, when all options look like variations of one idea, or to widen a decision before committing. Triggers include "concept fan", "zoom out", "what is this a way of doing", "wrong problem", "widen the options", "abstraction ladder". Do NOT use for analytical work like debugging, code review, or implementation tasks.
SaaS financial health advisor. Use when a user shares revenue or customer numbers, or mentions ARR, MRR, churn, LTV, CAC, NRR, or asks how their SaaS business is doing.
Pulls DOIs, arXiv ids, PMIDs, PMCIDs and ISBNs out of free text, deduplicated and normalized, with the character offset of each first occurrence. Called as POST /v1/text/extract-citations, it takes text, kinds and returns count, citations, byKind. An agent handed a references section, an email or a PDF dump has to find the identifiers before it can look any of them up, and a model asked to do it by reading invents DOIs that resolve to nothing. The catalog already answers `crossref.doi-metadata` and `pubmed.citation-search`; neither could tell you what to ask them about. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.003, paid in USDC on Base over x402.
This skill is activated when users are preparing to apply a successful methodology (from others or their own past experience) to a new scenario. Typical trigger signals: "Company X succeeded with method X, we should try it too" "This worked for me before, let's keep doing it" "The industry best practice is Y". Scenarios where it should not be invoked: Users are facing repeated occurrences of the same type of problem and need execution rather than methodology selection. Difference from "Contradiction Analysis Method": This skill emphasizes "different problems require different methods due to their distinct natures", while the latter focuses on "identifying the most important problem".
Refactor Flutter/Dart code to improve maintainability, readability, and performance. This skill applies Dart 3 features like records, patterns, and sealed classes, implements proper state management with Riverpod or BLoC, and uses Freezed for immutable models. It addresses monolithic widgets, missing const constructors, improper BuildContext usage, and deep nesting. Apply when you notice widgets doing too much, performance issues from unnecessary rebuilds, or legacy Dart 2 patterns.