lazy vs Delimit
lazy is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑01.
lazy is a plugin bundle for AI coding tools published by dstoic. No marketplace we read lists it any more. Delimit is an MCP server published by delimit-ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-06. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace digital-stoic-org/agent-skills | Removed on 2026-11-01 Version: 0.1.1 Forks (GitHub): 7 Stars (GitHub): 21 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.10.4 Downloads/month (npm): 5 560 Downloads/week (npm): 2 503 Forks (GitHub): 5 Stars (GitHub): 23 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 4.22.0 Downloads/month (npm): 5 560 Downloads/week (npm): 2 503 Forks (GitHub): 5 Stars (GitHub): 23 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | lazyno longer listed · | Delimit |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 21 | 23 |
| Forks (GitHub) (differs) | 7 | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (delimit-cli) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/digital-stoic-org/agent-skills | github.com/delimit-ai/delimit |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of lazy
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Close the loop between what you keep asking your assistant for and reusable skills: scan your transcripts for recurring patterns, draft a skill in this library's format, test its…
-
Create new skills, improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to…
-
Build, enhance, validate, and package Claude skills end-to-end. Coordinates skill-builder, skill-enhancer, quality-checker, and skill-packager via the skill-architect agent.
-
Create, evaluate, and iterate on high-quality agent skills with structured guidance, quality scoring, and best-practice enforcement.
-
A thin SkillSpec guide that lets agents inspect, import, route, run, and prove SkillSpec-backed skills from chat.
-
Ask 'should this become a skill?' before every task: a five-step checklist (repeatable, automatable, already ours, already someone else's, else create and validate it) plus an…
What each says it does
lazy
Lazy skill demand capture: declare placeholder skills that intercept trigger keywords and log hits to measure real demand before building the full implementation. Toggle off to pause capture.
Delimit
One workspace for every AI coding assistant. Shared tasks, memory, and governance.
How to run each
lazy
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Delimit As a local MCP server: npm package
claude mcp add --transport stdio delimit -- npx -y delimit-cli
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: lazy · What it can do: Delimit · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.