<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated 1d ago

by open-mercato

skills

Enterprise AI Engineering skills we coined at Open Mercato (1.2M+ lines of code ERP built with AI)

  • Active — Updated in the last 14 days
View on GitHub (opens in a new tab)

271 GitHub stars (271)

+52 in 30 days

Stars gained per day · daily snapshots since Sep 26
Stars gained per day, Sep 26 to Nov 5: +63 in total; the busiest day was Oct 8 with +6 stars.Sep 27: 0 starsSep 28: 0 starsSep 29: 0 starsSep 30: +2 starsOct 1: 0 starsOct 2: +2 starsOct 3: +4 starsOct 4: 0 starsOct 5: +1 starsOct 6: +2 starsOct 7: +2 starsOct 8: +6 starsOct 9: +4 starsOct 10: 0 starsOct 11: +2 starsOct 12: +2 starsOct 13: +1 starsOct 14: +5 starsOct 15: 0 starsOct 16: +1 starsOct 17: +4 starsOct 18: 0 starsOct 19: +1 starsOct 20: +1 starsOct 21: +2 starsOct 22: 0 starsOct 23: 0 starsOct 24: 0 starsOct 25: 0 starsOct 26: +1 starsOct 27: +1 starsOct 28: +2 starsOct 29: +1 starsOct 30: +5 starsOct 31: +2 starsNov 1: +1 starsNov 2: +3 starsNov 3: +2 starsNov 4: 0 starsNov 5: +3 stars
Stars gained between daily snapshots
PeriodNew stars
Sep 270
Sep 280
Sep 290
Sep 30+2
Oct 10
Oct 2+2
Oct 3+4
Oct 40
Oct 5+1
Oct 6+2
Oct 7+2
Oct 8+6
Oct 9+4
Oct 100
Oct 11+2
Oct 12+2
Oct 13+1
Oct 14+5
Oct 150
Oct 16+1
Oct 17+4
Oct 180
Oct 19+1
Oct 20+1
Oct 21+2
Oct 220
Oct 230
Oct 240
Oct 250
Oct 26+1
Oct 27+1
Oct 28+2
Oct 29+1
Oct 30+5
Oct 31+2
Nov 1+1
Nov 2+3
Nov 3+2
Nov 40
Nov 5+3
  • 30 skills (30 skills found in its SKILL.md files)
  • 42 forks (42 forks)
  • 1d ago last update (Last updated 1d ago)

Install

Skills CLI

npx skills add open-mercato/skills

Asks which skills and agents to install. Just one: npx skills add open-mercato/skills --skill om-app-spec-writing — add -g for every project.

Claude Code

git clone https://github.com/open-mercato/skillscp -r "skills/skills/om-app-spec-writing" ~/.claude/skills/

Copies the om-app-spec-writing skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add open-mercato/skills

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md — showing the first 30 of 60 files.

  • om-app-spec-writing

    Write and review a business-level App Spec — domain model, workflows with ROI, stories with failure paths, platform gap mapping in atomic commits, phased rollout — before any feature spec exists. Feeds om-spec-writing via feature briefs. Use for "create an app spec", "define business requirements", "what should we build".

    skills/om-app-spec-writing/SKILL.md on GitHub (opens in a new tab)
  • om-apply-upgrade-notes

    Apply the skills collection's UPGRADE_NOTES.md after an upgrade. Re-syncs installed tracker and browser-provider descriptors while preserving local edits, reports custom-provider gaps, checks pipeline config and installed artifacts, and summarizes exactly what changed.

    skills/om-apply-upgrade-notes/SKILL.md on GitHub (opens in a new tab)
  • om-approve-merge-pr

    Approve (submit an approving review) and squash-merge a PR given only its number, refusing when the QA gate or a blocking label forbids it. Routes fixable blockers to om-auto-fix-pr (red CI via its --ci-only mode, or conflicts and review problems via the full loop). Optionally file a follow-up issue at the same time. Use when the user says "approve and merge PR 123", "ship PR 123", or gives a PR…

    skills/om-approve-merge-pr/SKILL.md on GitHub (opens in a new tab)
  • om-auto-audit-dependencies

    Audit third-party dependencies for known security advisories in any ecosystem — reads every lockfile, uses the native audit tool where one exists and the OSV database otherwise, and files one deduplicated issue per vulnerable package with its upgrade path. For code-level security review use om-auto-sec-report. Use for "audit dependencies", "check for vulnerable packages", "security advisories".

    skills/om-auto-audit-dependencies/SKILL.md on GitHub (opens in a new tab)
  • om-auto-continue-pr-loop

    Advanced om-auto-continue-pr for PRs started by om-auto-create-pr-loop — claims the PR, resumes from the first non-done PLAN.md Tasks row in an isolated worktree, keeps the per-step commit and checkpoint discipline (integration tests + screenshots for UI), runs the full gate at completion, keeps spec-only design PRs design-only (implementation ships on its own PR via om-auto-implement-spec), and…

    skills/om-auto-continue-pr-loop/SKILL.md on GitHub (opens in a new tab)
  • om-auto-continue-pr

    Resume any open PR — started by `om-auto-create-pr` or opened outside the pipeline. Claims it, resumes in an isolated worktree from the first unchecked step of its execution plan; a PR with no plan is adopted — the goal is reconstructed from its description, comments, review feedback, linked issues and diff, then executed. Usage - /om-auto-continue-pr <PR-number>

    skills/om-auto-continue-pr/SKILL.md on GitHub (opens in a new tab)
  • om-auto-create-pr-loop

    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.

    skills/om-auto-create-pr-loop/SKILL.md on GitHub (opens in a new tab)
  • om-auto-create-pr

    Run an arbitrary autonomous task end-to-end and ship it as a PR against the configured base branch. Drafts a Progress-tracked execution plan, commits on a fresh worktree branch, implements phase-by-phase, runs the configured validation gate, applies pipeline labels. Long plans hand off to om-auto-create-pr-loop automatically. Resumable via om-auto-continue-pr.

    skills/om-auto-create-pr/SKILL.md on GitHub (opens in a new tab)
  • om-auto-fix-issue

    Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain (om-verify-in-repo, om-root-cause, om-fix, om-open-pr, om-auto-review-pr, om-auto-qa-pr for UI fixes) or the feature route (spec via om-auto-write-spec, built via om-auto-implement-spec). Isolated wor…

    skills/om-auto-fix-issue/SKILL.md on GitHub (opens in a new tab)
  • om-auto-fix-pr

    Drive an open PR to merge-ready from its number — merges the latest base, then loops review-autofix (om-auto-review-pr), built-in CI stabilization, and UI verification (om-auto-qa-pr) until approvable, green, and QA-evidenced. A --ci-only mode drives just CI green on a PR or a plain branch. Files follow-up issues for nits, normalizes labels, hands off to om-approve-merge-pr — never merges itself.…

    skills/om-auto-fix-pr/SKILL.md on GitHub (opens in a new tab)
  • 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 screensh…

    skills/om-auto-implement-spec/SKILL.md on GitHub (opens in a new tab)
  • om-auto-manage-issues

    Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, checks each issue against SDLC.md's Definition of Ready (READY_STATUS, not-ready comment), and flags feature issues lacking a covering spec (optionally authoring one with --write-missing…

    skills/om-auto-manage-issues/SKILL.md on GitHub (opens in a new tab)
  • om-auto-qa-pr

    QA a PR's UI change in a real browser through the configured browser-provider descriptor — first ensuring the PR has been reviewed (invoking om-auto-review-pr when it has not), then capturing screenshots and a pass/fail report, and optionally posting tracker evidence or self-QA labels without modifying source. Also runs in a local, tracker-less mode against the current worktree.

    skills/om-auto-qa-pr/SKILL.md on GitHub (opens in a new tab)
  • 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".

    skills/om-auto-qa-scenarios/SKILL.md on GitHub (opens in a new tab)
  • om-auto-review-pr

    Review or re-review a PR by number in an isolated worktree. Runs the `om-code-review` skill — or, for spec-only design PRs, a specification review — submits approve/request-changes, manages pipeline labels. On changes-requested, the autofix loop (fix/test/validate/re-review until merge-ready) runs on the automation's own PRs or with --autofix; other authors' PRs get review + handoff only. Usage -…

    skills/om-auto-review-pr/SKILL.md on GitHub (opens in a new tab)
  • om-auto-sec-report-pr

    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".

    skills/om-auto-sec-report-pr/SKILL.md on GitHub (opens in a new tab)
  • 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".

    skills/om-auto-sec-report/SKILL.md on GitHub (opens in a new tab)
  • 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.

    skills/om-auto-update-changelog/SKILL.md on GitHub (opens in a new tab)
  • om-auto-write-spec

    Autonomously turn a brief or FR issue into a spec landed on a ready PR — runs om-spec-writing --autonomous (defaults posted for override), attaches UI mockups and current-app screenshots as PR evidence when a browser provider exists, applies full SDLC labels, and emits PR/spec markers for chaining into om-auto-implement-spec. Use for "write a spec for X and open a PR", "spec this issue".

    skills/om-auto-write-spec/SKILL.md on GitHub (opens in a new tab)
  • om-backlog

    Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and rationale come for free. Refuses a brief that is not ready; shows the whole tree and waits before writing. Use for "build the…

    skills/om-backlog/SKILL.md on GitHub (opens in a new tab)
  • om-brainstorm

    Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill. Runs before om-spec-writing and om-prepare-issue. Use when the user says "should we build this", "let's think this through", "I have an idea", "is this worth doing".

    skills/om-brainstorm/SKILL.md on GitHub (opens in a new tab)
  • 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.

    skills/om-check-and-commit/SKILL.md on GitHub (opens in a new tab)
  • om-close-fixed-issues

    Close the tracker issues that recently merged PRs authoritatively fixed — via `fixes`/`closes`/`resolves` keywords or `closingIssuesReferences` — and post informational comments on issues whose PRs were closed without merging or merged into a non-base branch. Use for post-merge housekeeping and release prep. Respects claim locks and never acts on bare `#N` mentions.

    skills/om-close-fixed-issues/SKILL.md on GitHub (opens in a new tab)
  • om-code-review

    Review a diff, branch, or PR against correctness, security, breaking-change, and quality standards — runs the validation gate, applies the built-in checklist plus any repo-local one, and produces severity-ranked findings with an approve/request-changes verdict. The review engine behind om-auto-review-pr and om-review-prs.

    skills/om-code-review/SKILL.md on GitHub (opens in a new tab)
  • om-create-agents-md

    Write, rewrite, or refresh an AGENTS.md (repo root or one package/module) from the actual codebase — Always / Ask First / Never / Validation Commands rules, task checklists, real paths and commands. Follows a repo template when present, else a built-in default. Use for "write AGENTS.md for this package", "rewrite our AGENTS.md", "refresh AGENTS.md".

    skills/om-create-agents-md/SKILL.md on GitHub (opens in a new tab)
  • 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".

    skills/om-create-skill/SKILL.md on GitHub (opens in a new tab)
  • om-discover

    Guide a product discovery conversation and write product-brief.md with the problem, evidence, scope, decisions, and the next uncertainty to resolve. Use for product discovery, defining a product, or refreshing its brief. Supports existing products, client ideas, and own ideas.

    skills/om-discover/SKILL.md on GitHub (opens in a new tab)
  • om-eject-and-customize

    Take one part of an installed dependency into the repo for customization via the eject recipe the dependency ships — decision gate first, confirmation before any change, provenance recorded so later upgrades can diff. Stops when no recipe exists. Use for "eject this module", "fork the installed component", "customize beyond extension points".

    skills/om-eject-and-customize/SKILL.md on GitHub (opens in a new tab)
  • om-evolve-harness

    Turn a real agent failure into one reproducible eval-harness case plus the smallest knowledge change — failing case first, one knowledge owner, semantic assertions, before/after evidence through the repo's configured harness commands. Use for "add harness case", "agent got this wrong", "extend the harness", "rozszerz harness".

    skills/om-evolve-harness/SKILL.md on GitHub (opens in a new tab)
  • 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".

    skills/om-figma-design-with-ds/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.