dev
This skill should be used when the user needs the OmniSkill Developers crew — stress-testing a plan before building, planning and TDD workflows, live version-exact library docs, building MCP servers, scaffolding new skills, browser-testing a web app, searching, scraping or crawling websites, reading PDFs and books as Markdown, reverse-engineering how an app or site works, or persisting memory across sessions. Triggers on "/omniskill:dev", "grill me", "stress-test this plan", "set up TDD", "look up the docs for", "build an MCP server", "create a skill", "test my app in a browser", "scrape this site", "crawl", "search the web for", "how does this app do X", "reverse engineer", "convert this PDF", "render this JS page", "moli", "read this book".
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- dev
- description
- This skill should be used when the user needs the OmniSkill Developers crew — stress-testing a plan before building, planning and TDD workflows, live version-exact library docs, building MCP servers, scaffolding new skills, browser-testing a web app, searching, scraping or crawling websites, reading PDFs and books as Markdown, reverse-engineering how an app or site works, or persisting memory across sessions. Triggers on "/omniskill:dev", "grill me", "stress-test this plan", "set up TDD", "look up the docs for", "build an MCP server", "create a skill", "test my app in a browser", "scrape this site", "crawl", "search the web for", "how does this app do X", "reverse engineer", "convert this PDF", "render this JS page", "moli", "read this book".
- when_to_use
- Use for engineering workflow and tooling tasks. For ordinary code edits in an existing repo, work directly instead.
- allowed-tools
- Read Glob
03 SKILL.md 正文
01 — Developers
Ship code faster, from scaffold to QA. Your build team.
Pick the specialist
| Skill | Use when |
|---|---|
grill-me |
Pressure-testing a plan or design before building it |
superpowers |
Structured planning and test-driven development on a real feature |
context7 |
Needing the current API of a library — never answer library questions from memory |
mcp-builder |
Wiring Claude to an external tool or API as an MCP server |
skill-creator |
Turning a repeated workflow into a reusable skill |
webapp-testing |
Verifying a web app actually works in a browser |
scrapling |
Reading the web: search, fetch past bot walls, map or crawl a site, pull structured data |
pdf-to-md |
Making a PDF or a whole book readable by AI: Markdown chapters with page anchors, audited word by word against the PDF so nothing is dropped silently |
moli |
Reading JavaScript pages without Chromium: moli fetch, scrapling's --engine moli; built from source, with measured limits |
rea |
How a shipped app or site works without its source: Electron bundles, .NET, APKs, binaries, with evidence |
claude-mem |
Carrying durable knowledge across sessions |
Load it
Read ${CLAUDE_SKILL_DIR}/../<skill>/SKILL.md and follow it. Its paths that start with the CLAUDE_SKILL_DIR placeholder mean its own folder, ${CLAUDE_SKILL_DIR}/../<skill>/: only the invoked skill gets the placeholder filled in, and Bash never sets it, so write that full path into any command it gives you.
Routing notes
context7 is near-free and high-value: any question about a library's API, config, or version behaviour should route here before answering. Guessing at library APIs from memory is the single most common source of wrong code.
Engine order for reading the web: plain request, then moli for JavaScript, then Chromium for bot walls or app testing. Moli does not replace the Playwright MCP.
scrapling is for other people's sites; webapp-testing is for the user's own app. context7 still comes first for library docs.
superpowers and webapp-testing compose — plan and build with the first, prove it works with the second.
grill-me runs before both. When someone arrives with an approach already in mind and the stakes are real, interrogate it first — an hour of questions is cheaper than a week down the wrong branch.
04 同仓库更多 Skills
xlsx
Excel with live formulas. OmniSkill Operations crew — adapter for the xlsx skill, which installs separately.
webapp-testing
Browser-test a web app. OmniSkill Developers crew — drives a real browser to verify user flows, catches console and network errors, and writes tests that do not flake.
web-artifacts
shadcn HTML artifacts. OmniSkill Design crew — bundled copy of the Web Artifacts skill.
video
Script and produce video. OmniSkill Social crew — structures short-form and long-form video around retention, with shot lists, captions, and platform-specific delivery.
vgpu
暂无简介
uisfx
暂无简介