Loading...
Loading...
Found 3,300 Skills
Write bug bounty reports that get triaged quickly and rated accurately — clear impact statements, minimal reproduction steps, and professional tone. Use before submitting any vulnerability report.
Security report over a window — merged PRs since a date or PR number (default last 7 days), or one branch or spec. Runs `om-auto-sec-report-pr` per unit, aggregates severity-ranked findings, a risk heatmap, and one "go deeper" list into one redacted report, kept local by default or shipped as a docs-only PR. Use for "weekly security report", "security review of everything merged since X".
Read-only router for "which skill should I use?", "what do I do next?", "how do I do X here?". Builds the answer at run time from the repo's AGENTS.md Task Router, the skills actually installed, optional repo workflow data, and knowledge sources — then recommends and hands back control. Never runs the pipeline itself.
Paranoid OWASP-style security analysis of ONE unit (a PR, spec, or branch diff) — severity-ranked findings, non-obvious attack vectors, same-pattern hotspots, and "go deeper" follow-up runs. Writes a redacted report (live exploitable details withheld), kept local by default or shipped as a docs PR, or a fragment for `om-auto-sec-report`. Use for "security review of PR 123".
Settle every decision behind a plan before anything gets built, in rounds. Opens with a kill condition that can end in a cut, closes with a decision record. Use when a plan, feature, or design needs pressure-testing before a spec exists, when the user says "interview me", "grill me", "pressure-test this", "poke holes in this", or "before we plan this", and when another skill needs the decisions settled before it writes anything. Draws the design tree as a page when it grows or when asked to "show me the tree".
Query available AI models, list model aliases, and browse the full model catalog from the CLI. Filter by provider, search by capability, and resolve model name variants.
Use when starting any task, as its first step, to decide whether an installed skill should drive it. Searches the whole installed catalogue, including skills the host hides from its listing, by concepts in English and Russian, then opens the matching SKILL.md. Triggers - "which skill", "find a skill", «какой скилл», «найди скилл», «первый шаг». NOT for building or auditing a skill (make-skill).
Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.
Gate 4: API contracts document - defines component interfaces and data contracts before protocol/technology selection. Large Track only.
Create a product requirements document through a guided product interview.
Perform a final compliance gate on the CUMCM 2026 paper and supporting materials: verify the abstract and page numbering, absence of a table of contents, main-text page count, anonymization, AI declaration and details, complete source code, file sizes, and manifest consistency, and build the submission archive. For CUMCM submission preparation only.
Interview the user in batches of 10 questions with recommended answers to sharpen a plan, an idea or an app before building. Use when the user says grill me, wants a rigorous interview, or when create-software, create-internal-app or create-landing needs a confirmed brief.