open-mercato · Agent Skills
74 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.
om-auto-implement-spec
Implement an existing spec and ship a verified, reviewed, ready PR. Resolves the spec by path, name, issue, or spec-PR number (clean stop with candidates when not found). A spec PR stays design-only — implementation ships on its own PR referencing it. Delegates to om-auto-create-pr (om-auto-continue-pr for an existing implementation PR), then runs the review loop and UI verification with screenshots. Use for "implement the spec X", "build spec from issue 123".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-auto-merge-triage
Rank open PRs for the automerge queue using eligibility tiers and AI judgment of meaningful fixes close to merge, including older PRs with screenshots and bounded requested changes. Exclude untrusted authors and apply the queue label only after human confirmation. Feeds om-auto-merge-buddy.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-auto-qa-scenarios
Turn a window of merged PRs (date, PR-number floor, or last 7 days) into a manual QA scenarios report for human testers — P0/P1/P2 routes with where to click, what to verify, what can go wrong — as markdown + HTML under paths.qa, shipped as a docs PR via om-auto-create-pr. Use for "what should QA test this week".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-auto-sec-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".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-auto-update-changelog
Draft a CHANGELOG.md release entry in an emoji-driven format for every PR merged since the last release, then delegate to om-auto-create-pr so it lands as a docs PR against the configured base branch. Honors the Supersede Credit Rule and verifies every credit against commit authorship, so carry-forwards and umbrella merges credit the contributor rather than the merger. Use at release time.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-check-and-commit
Verify that the current branch is ready to publish by running every configured validation command in order, fix straightforward failures (including locale-file drift when the repo checks it), and once everything passes commit and push the current branch. Use when the user asks to check the branch, make CI-style verification pass, then commit and push.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-create-skill
Author a new OM skill from a brief, or split an oversized SKILL.md into layered references/ files — conservatively, behind the lint + completeness gate. Knows the layering philosophy, lint invariants, tracker abstraction, and the cross-skill contract, so output matches house conventions. Use for "create a skill for…", "new om-skill", "split this skill into references".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-figma-design-with-ds
Design in a design tool (Figma or similar) on the repository's design system — write a brief for a new screen using only the contract's tokens, components and archetypes, or audit an existing design against the contract with a ranked remediation plan. Tool access goes through a configured provider. Use for "figma mockup", "audit this figma design".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-gap-analysis
Grounded gap analysis of requirements against the platform an app builds on — client docs become an Epic/Story tree whose every coverage verdict is re-run by executable gates against a validated platform checkout, scored in atomic commits, license-tier-tagged, summarized with a backlog. Use for "gap analysis", "what does the platform already cover".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-harness
Shared internal runtime for configurable staged-only implementation workers, evidence-gated work packets, and multi-model review councils. Use indirectly through om-fix-issue, om-implement-feature, or om-setup-agent-harness; do not use it to publish, commit, push, or open a pull request.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-implement-feature
Design and implement a feature through existing spec, testing, environment, and review skills, then leave a verified staged branch for human review without committing, pushing, or opening a pull request. Use when the user says "implement this feature but stop before PR", "leave the feature staged", "staged feature build", "zaimplementuj bez PR", or "zostaw feature staged".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-implement-feature-multi-optimized
Thin combined alias for om-implement-feature that uses configured implementation workers and independent review advisors, then leaves the verified feature staged and unpublished. Use when the user says "multi optimized feature", "workers plus model council", "cheap cross-model staged feature", or "zaimplementuj feature multi optimized".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-implement-feature-optimized
Thin worker-optimized alias for om-implement-feature that delegates bounded implementation packets to configured models, then leaves the verified feature staged and unpublished. Use when the user says "optimized feature build", "use model workers", "cheap staged feature", or "zaimplementuj przez workerów".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-integration-tests
Use when live-app integration or E2E tests need running, creating, or debugging, e.g. 'add browser coverage for this flow'. Explore with the configured browser provider, preserve repository-native runners, reuse the shared test environment, and diagnose failures from concrete artifacts.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-mockup-prototype
Build a neutral clickable low-fi prototype from a product brief during discovery, after the first synthetic panel and before refreshing the brief or drafting a backlog. Preserve business rules and explicit assumptions, simulate the chosen flow locally, and verify navigation and relevant states in a browser. Use for discovery wireframes or testing a flow before detailed design.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-pr-autopilot
Diagnose what state one open PR is actually in — unfinished plan steps, missing review, unresolved conversations, red CI, base conflicts, missing QA evidence, merge-ready — then run the matching chain of om- skills in order and publish a status report. Use for "finish PR 123", "what is left on PR 123", "drive PR 123 to the end".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-prepare-issue
Create one well-formed tracker issue from a brief without implementing it — dedupes against existing issues and PRs, links a covering spec (authoring one via om-auto-write-spec on a design-only PR when a feature needs it), attaches user-provided images as tracker evidence, otherwise embeds step-by-step guidance, and applies SDLC labels on creation. For existing issues use om-auto-manage-issues. Use for "file an issue for X", "park this idea".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-prepare-test-env
Use when tests or browser QA need a reusable local environment, e.g. 'set up the test app'. Discover the stack, generate cross-platform launch scripts, provision the configured browser provider autonomously, and write the shared test-env descriptor for UI and integration-test skills.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-qa-buddy
Runs a manual QA session for a PR, issue, or branch — publishes an interactive runbook the tester works through in parallel from the moment a plan exists, updated with AI verdicts and bugs at the end. Never touches the tracker itself. Unlike om-auto-qa-pr's automated sign-off, this is human-in-the-loop and grows a local QA knowledge base. Use when the user says "test this for me", "QA this PR", "find bugs in this change", "walk through this issue for bugs".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-setup-agent-harness
Configure or diagnose the staged-only multi-model harness, including selectable implementation workers, review advisors, high-assurance packet policy, provider probes, and optional Claude model-matrix output style. Use when the user says "set up the agent harness", "configure multi-model reviewers", "choose worker models", "check harness setup", "skonfiguruj harness", or "sprawdź modele".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-setup-discovery-pipeline
Use when a repository needs product discovery gates alongside its delivery pipeline, e.g. 'set up discovery'. Configure product roles and settings, extend SDLC.md with readiness and protected-decision rules, and add the research directory and AGENTS.md routing. Set up delivery first if missing; re-run with --refresh. Product skills work without it.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-share-this-session
Publicly share a sanitized coding-agent session plus a ZIP of the files it generated, then file a harness-feedback issue at the configured destination — local sanitization, full privacy review, exact fresh consent first. Use for "share this session", "report this agent run", "udostępnij tę sesję". Never for telemetry or without consent.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-synthetic-users
Builds a panel of personas from real material, interviews them under decision pressure (never stated preference), and walks a flow through their eyes — on a brief, a spec, a prototype, or the running app. Fresh panels, repeated runs, believe only what repeats; saturation and a parity check against real interviews when they exist. Three stances. Output is hypotheses tagged synthetic, never evidence. Use for "synthetic users", "walk this as the persona".
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13
om-ux-setup
Use when a repository needs its design contract extracted or refreshed, e.g. 'set up UX checks' or after design-system changes. Write tokens, components, screen archetypes, and conventions to .uxproof/, including versioned dependency design systems, so UX skills assess against this repository's system. Extract the contract without reviewing the UI.
- 1h installs
- 1
- GitHub stars
- 279
- Updated
- Nov 13