Emdash Skills
A cross-tool product-building system that turns short prompts into quality-gated applications deployed on Cloudflare Workers.
- Source repo
- heymegabyte/agent-skills
- Stars
- ★ 26
- Last updated
- 3d ago
- License
- NOASSERTION
- Primary language
- TypeScript
- FA score
- 38/100 · Blocked
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A solo founder wants to turn a one-line SaaS concept into a brief, architecture, implementation slices, tests, and a Cloudflare Workers deployment.
- Not a fit if
- Teams deploying to clouds other than Cloudflare Workers
- Teams unwilling to wire up Clerk, Stripe, Resend and other external services
- Small changes that cannot absorb mandatory multi-breakpoint and a11y gates
- Source review
- 38/100 · Blocked 3 safety controls not found
What does this agent do, and when should you use it?
Emdash Skills is a collection of skills, rules, agent roles, commands, templates, and helper scripts for solo SaaS development rather than a single resident service. The repository describes 19 skill categories, 163 reference documents, 20 agent roles, more than 20 slash commands, and generated rule variants for 32 coding-tool formats. A router selects a small task-specific skill set, after which the workflow separates architecture, parallel implementation, verification, and deployment. Its preferred stack centers on Cloudflare Workers, Hono RPC, Drizzle v1, and D1 or Neon, with documented integrations including Angular, Ionic, PrimeNG, Clerk, Stripe, Inngest, Sentry, and PostHog. Delivery is bounded by Playwright, visual, Lighthouse, axe-core, SEO, console, placeholder, and readability gates before deployment to Cloudflare Workers. It is a strong fit for adopters who want an opinionated, end-to-end product process; teams using different clouds, frameworks, or acceptance standards should expect to curate and adapt its rules.
The workflow begins with a user prompt and a skill router that loads the smallest relevant subset; 01-OS is always included, while a product build commonly proceeds through 02-Brief, 05-Arch, 06-Build, 07-QA, and 08-Deploy. The architecture phase produces a repo map and task graph and identifies parallel seams; build work can then be divided across frontend, backend, content, media, and tests, while verification roles cover deployment, SEO, visual quality, and accessibility. The repository supplies structured artifacts such as acceptance-criteria.md, adr-template.md, product-intent.yaml, qa-report.json, and task-graph.json, plus scripts including bin/emdash-quick-lint, bin/emdash-secret-scan, bin/emdash-cost-check, scripts/validate-skills.sh, and scripts/visual-tdd-loop.sh. Commands include /saas, /forge-from-openapi, /run-evals, /audit-doctrine, and /audit-mcp-fleet; bin/forge-skill-from-openapi.mjs generates a SKILL.md and command scaffold from an OpenAPI specification. Separate categories cover DOCX and XLSX read/write operations, PDF parsing and generation, PPTX generation, HTTP MCP servers on Workers, stdio MCP templates, OpenAPI-to-MCP forging, and registry publishing. The documented release path checks Playwright flows at six breakpoints, visual scoring, Lighthouse, axe-core, SEO, browser-console output, placeholder content, and Flesch readability before deploying to Cloudflare Workers.
- A solo founder wants to turn a one-line SaaS concept into a brief, architecture, implementation slices, tests, and a Cloudflare Workers deployment.
- A maintainer needs to add authentication, billing, webhooks, analytics, or another feature to an existing web application using a test-first implementation sequence.
- A platform team wants to distribute a common engineering doctrine across Cursor, Windsurf, Copilot, Codex, Claude Code, Aider, Cline, and other coding environments.
- A backend developer wants to generate an MCP skill and command scaffold from OpenAPI or create an HTTP MCP server on Workers.
- A web team is rebuilding a marketing site, portfolio, or content property and needs consistent SEO, visual, accessibility, and multi-breakpoint acceptance checks.
- A mixed technical and business organization wants one framework covering C-suite, finance, compliance, product-management, and DOCX, XLSX, PDF, or PPTX workflows.
How do you install or deploy this agent?
The recommended GitHub Skills command is gh skill install heymegabyte/claude-skills. For Claude Code, run claude plugin install heymegabyte/claude-skills; for npm, run npm i @heymegabyte/claude-skills; for JSR, run npx jsr add @heymegabyte/claude-skills. The documented Codex path is git clone https://github.com/heymegabyte/claude-skills ~/.codex/skills, while a generic manual installation clones the repository into ~/.agentskills. These are alternative installation methods, not cumulative requirements. Deploying the default product stack also requires network access, a writable project filesystem, and a Cloudflare Workers environment. Credentials are feature-dependent: documented examples check STRIPE_*, CLERK_*, INNGEST_*, and CLOUDFLARE_API_KEY, while map-based local-business projects additionally require GOOGLE_MAPS_API_KEY and GOOGLE_PLACES_API_KEY.
How do you use this agent?
After installation, issue a product or engineering request inside a supported coding tool. A documented first invocation is Build acmebilling.dev — recurring subscription billing for indie SaaS founders. Stripe-native, Clerk auth, Inngest for retry workflows.; it routes through skills 01, 02, 03, 05, 06, 07, 08, and 13 and checks the Stripe, Clerk, Inngest, and Cloudflare credentials before scaffolding. For an existing project, use a request such as Add a magic-link auth flow to acme.dev — passwordless email via Resend, Clerk session, redirect to /dashboard., which invokes architecture, build-slice, and Playwright E2E work. If only coding guidance is needed, use the generated rule file for the target platform; for a complete build, allow the router to select skills and proceed through every hard gate before Workers deployment. The supplied material does not define one universal configuration file or credential list across all platforms, so keys must be prepared for the selected skills and integrations.
What are this agent's strengths and limitations?
- Its 19 skill categories and 163 reference documents span briefs, architecture, implementation, QA, deployment, growth, document processing, and MCP authoring.
- It generates native rule variants for 32 tool formats and provides explicit installation paths for Codex and Claude Code, enabling reuse across coding environments.
- Acceptance gates are measurable: zero Playwright failures at six breakpoints, Lighthouse accessibility of at least 95, zero axe-core violations, zero console errors, and zero placeholders.
- It includes auditable operational assets such as task graphs, JSON QA reports, Semgrep rules, secret scanning, cost checks, and a visual TDD loop.
- The OpenAPI forge can generate MCP skill scaffolding, with both Workers-based HTTP MCP and stdio server patterns documented.
- The defaults are strongly oriented toward Cloudflare Workers, Hono, Drizzle, Angular/Ionic/PrimeNG, and Bun; other clouds, frameworks, and runtimes require rule and scaffold changes.
- A full deployment can depend on numerous external services and credentials, including Cloudflare, Clerk, Stripe, Resend, Inngest, Sentry, PostHog, and Google Maps, increasing configuration, cost, and vendor-management overhead.
- Mandatory multi-breakpoint testing, visual review, accessibility, SEO, and readability gates add execution time and tooling overhead even for relatively small changes.
- Repository metadata reports NOASSERTION for the license, while the README badge and license section identify the Rutgers License; adopters should inspect the LICENSE terms directly.
- The supplied material describes broad automation and thresholds but does not provide a measured platform-compatibility matrix, benchmark results, or cost data for every deployment scenario.
How does this agent compare with similar options?
Compared with using a single coding-rule file, Emdash Skills adds skill routing, specialized agent roles, slash commands, templates, verification scripts, and deployment gates. It provides both modern native formats and some legacy single-file formats for tools such as Cursor, Windsurf, Copilot, and Augment; modern variants use platform-specific frontmatter, while legacy variants are primarily plain instruction files. The repository does not claim that all environments execute identical capabilities: the variants carry the rules, while the opinionated product workflow and default deployment path remain centered on its skill graph and Cloudflare stack.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Emdash Skills This agent | 38 · Blocked | Agent plugin / skillFree + model costs | ★ 26 | 3d ago | TypeScript | Codex · Claude Code |
| Claude Forge | 55 · Major gaps | Agent plugin / skillFree + model costs | ★ 875 | 2mo ago | Shell | Claude Code |
| Hercules Testing Agent | 49 · Major gaps | CLIFree + model costs | ★ 1.2k | 15d ago | Python | — |
| OpenConnector | 71 · Some gaps | Self-hosted serviceFreemium | ★ 6.2k | today | TypeScript | — |
How does FollowAgents rate this agent?
Why each dimension lost points
The adapter removes several credentials and GitHub write variables, avoids logging raw command contents, and constrains workspace paths. However, Codex and Claude are explicitly launched with approval and sandbox bypass flags, while CLAUDE.md and skills make broad autonomy and silence-as-approval defaults; least privilege and user confirmation score 0. Deployment, publishing, and external-service effects lack consistent confirmation or recovery safeguards. PII utilities and a security reporting address provide only partial evidence. Publisher fields are visible, but the license contains hard-to-interpret legal terms, so attribution scores only 1.
The router, skills, and plugin manifests provide a recognizable operating structure, but README, plugin manifests, and AGENTS.md disagree on category, agent, rule, and platform counts, reducing self-consistency. CI says it covers only a limited verified test subset and notes unresolved environment-dependent issues. The adapter handles timeouts, empty replies, and failure events, supporting a failure-message score of 2.
The README gives several product scenarios, a routing table, and reusable prompts; skill frontmatter also specifies triggers. The product spans many tools and work types, but capability boundaries are weak, and AGENTS.md/CLAUDE.md direct broad permissions and automatic implementation, so boundaries score 0. Environment guidance is extensive, though many referenced rules are outside the sample and platform/version claims conflict.
The README, router, templates, skill directories, and installation commands provide basic structure, onboarding, and examples. Category numbering has gaps, and counts disagree across the README, plugin metadata, and AGENTS.md. The license file calls itself the Rutgers License but contains nonstandard terms whose legal effect is unclear, so it does not establish clear usable licensing and scores 0. A version and security reporting path are visible, while changelog, support, and maintenance commitments have limited evidence.
Routing, templates, agent roles, and quality gates could make product-building workflows more actionable, and the README includes several end-to-end prompts. Utility and cost control are mostly asserted through descriptions and gates, with no verifiable outcome evidence in this sample. Broad automation and many external services also add operating burden, so cost-benefit scores 1.
Some README claims have partial counterparts in manifests, scripts, skills, and workflows, but counts, scope, and version descriptions conflict; many quality gates and product outcomes remain assertions. The sample includes test files and limited CI configuration, but this review does not claim tests were run or passed. Fact and inference are not consistently separated, so scores remain conservative.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- The adapter starts Codex/Claude with approval and sandbox bypass modes; combined with repository instructions permitting broad autonomous actions, this is an unresolved permissions red line.
- The license terms are difficult to interpret; have qualified counsel review them before adoption.
- README, plugin manifests, and AGENTS.md disagree on counts for scale, categories, and platform support; files outside the sample remain unknown.
Maintain this project? Add the FARS badge to your README
[](https://followagents.com/en/agents/heymegabyte-claude-skills)<a href="https://followagents.com/en/agents/heymegabyte-claude-skills"><img src="https://followagents.com/badge/heymegabyte-claude-skills.svg" alt="FARS review"></a>Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
v7.2.1 Emdash Skills v7.2.1
Release notes excerpt
Full Changelog: https://github.com/megabytespace/claude-skills/compare/v7.2.0...v7.2.1View on GitHub ↗ -
v7.2.0 Emdash Skills v7.2.0
Release notes excerpt
Full Changelog: https://github.com/megabytespace/claude-skills/compare/v7.1.0...v7.2.0View on GitHub ↗ -
v7.1.0 Emdash Skills v7.1.0
Release notes excerpt
Full Changelog: https://github.com/megabytespace/claude-skills/compare/v7.1.0...v7.1.0View on GitHub ↗
FAQ
Must every project deploy to Cloudflare Workers?
Which API keys are required before starting?
STRIPE_*, CLERK_*, INNGEST_*, and CLOUDFLARE_API_KEY; the local-business map example also requires Google Maps and Places keys.Can I adopt only the coding rules?
What can prevent a deployment?
Is the license designation unambiguous?
Thanks — we use this to improve the page.