Monorepo containing the official TypeScript Contracts, CLI (
nlb), Model Context Protocol (MCP) Server, and AgentSkill for Next Level Builders Directory.
nlb-directory-toolkits/
├── packages/
│ ├── contracts/ # @nextlevelbuilder/contracts: Zod schemas, 17 block types, 5 templates, SHA-256 hasher, wire APIs, affiliate contracts
│ ├── cli/ # @nextlevelbuilder/cli: `nlb` binary (validate, preview, submit, list, get, rankings, stats, traffic, doctor, vote, keys, upload, checkout, affiliates)
│ └── mcp/ # @nextlevelbuilder/mcp: Model Context Protocol server (stdio & Cloudflare Workers, 39 tools)
├── skills/
│ └── nlb-submit/ # SKILL.md: Standard AgentSkill for Claude Code, Cursor, Codex, OpenCode, skills.sh
└── docs/ # Detailed guides for CLI, MCP, Contracts, and Architecture
# Validate schema and compute SHA-256 canonical hash:
npx @nextlevelbuilder/cli validate product.json
# Render terminal ASCII box preview:
npx @nextlevelbuilder/cli preview product.json
# Generate a starter template:
npx @nextlevelbuilder/cli template dev-tool --out product.json
# Submit revision to directory review queue (supports Polar checkout if slot needed):
npx @nextlevelbuilder/cli submit product.json --org <YOUR_ORG_UUID> --api-key <YOUR_API_KEY>
# View organic community rankings / leaderboard:
npx @nextlevelbuilder/cli rankings weekly
# Check live platform metrics and statistics:
npx @nextlevelbuilder/cli stats
# Query your product's NLB page traffic using the configured API key:
npx @nextlevelbuilder/cli traffic my-awesome-tool --json
# Export raw LLM-optimized Markdown for any product:
npx @nextlevelbuilder/cli get my-awesome-tool --markdown
# Check database and endpoint connectivity:
npx @nextlevelbuilder/cli doctor
# Affiliate program: your level, budget, referral links and earnings:
npx @nextlevelbuilder/cli affiliates program
npx @nextlevelbuilder/cli affiliates me
npx @nextlevelbuilder/cli affiliates links create --discount-bps 1000 --destination /courses{
"mcpServers": {
"nlb-directory": {
"command": "npx",
"args": ["-y", "@nextlevelbuilder/mcp"]
}
}
}{
"mcpServers": {
"nlb-directory": {
"command": "npx",
"args": ["-y", "@nextlevelbuilder/mcp"],
"env": {
"NLB_API_KEY": "nlb_live_your_key_here"
}
}
}
}EN — Members can read the program, join after accepting the Affiliate Agreement, create and tune referral links within their incentive budget, and follow conversions, commissions and payouts through nlb affiliates … or the affiliate_* MCP tools. Finance operators with the mcp:operator scope get read-only previews, conversion holds and draft payout batches (affiliate_admin_*); no tool sends money, reads bank or identity data, or approves anything that needs a second operator. See MCP Reference and CLI Reference.
VI — Thành viên có thể xem chương trình, tham gia sau khi đọc và chấp nhận Affiliate Agreement, tạo và chỉnh link giới thiệu trong ngân sách ưu đãi của mình, rồi theo dõi chuyển đổi, hoa hồng và chi trả qua nlb affiliates … hoặc các MCP tool affiliate_*. Operator tài chính có scope mcp:operator được xem trước, tạm giữ chuyển đổi và tạo đợt chi trả nháp (affiliate_admin_*). Không tool nào chuyển tiền, đọc dữ liệu ngân hàng hay giấy tờ tùy thân, hoặc phê duyệt thao tác cần người thứ hai.
Every listing in Next Level Builders is composed of modular, strongly-typed blocks with id and props:
hero: Main showcase with headline, subheadline, CTA, and badge.carousel: Multi-slide image rotation with titles and image URLs.mediaGallery: Responsive multi-column screenshot and video gallery.quote: Testimonials, verified reviews, and author credentials.grid: Multi-column feature highlights and capability cards (1-3 cols).changelog: Version histories, release dates, and categorized change notes.roadmap: Planned, in-progress, and completed development milestones.pricing: Tiers with billing periods, feature lists, and popular badges.faq: Accordion Q&A items.techStack: Categorized technology and runtime badges.liveDemo: Embedded interactive sandbox (iframe,height,sandboxTokens).cta: High-conversion call-to-action banner.founder: Founder profiles, bios, and verified social links.verification: Metric and platform provenance proofs.milestones: Key historical achievements with metrics.caseStudy: In-depth customer story with problem, solution, and quantifiable results.analytics: Real NLB product page traffic with configurable title and 7/30/90-day period. Publishing opts into public aggregate totals and daily series; detailed traffic remains organization-authorized. See Analytics block and traffic contracts.
- Node.js >= 18.0.0
- pnpm >= 9.0.0
# Install dependencies
pnpm install
# Build all packages in topological order
pnpm build
# Run comprehensive test suite across all packages (Vitest)
pnpm test
# Typecheck with TypeScript strict mode
pnpm type-check- CLI Reference — Comprehensive command and flag documentation
- MCP Reference — Tool specifications and Cloudflare Workers deployment
- Contracts Reference — Zod schemas and layout templates
- System Architecture — Core/adapter boundary and cryptographic design
MIT © Next Level Builders
Release workflow publishes all three packages on a
v<version> tag whose commit belongs to main. The tag must match every package
version. Merge a reviewed version change first, then create the matching tag.
Manual workflow runs build, test, type-check and upload npm-packages tarballs
without publishing. Release builds use Node 24 and npm 11.19.0. pnpm packs the
workspace dependencies into registry-compatible versions; npm publishes those
archives using GitHub OIDC and automatically attaches provenance.
Configure each package's npm Trusted Publisher with:
- Provider: GitHub Actions
- Repository:
nextlevelbuilder/nlb-directory-toolkits - Workflow filename:
release.yml - Environment: leave empty
- Allowed action: direct
npm publish
No NPM_TOKEN or NODE_AUTH_TOKEN repository secret is required. npm requires a
package to exist before trust can be configured. For the first release only, run
the workflow manually, download and inspect its three tarballs, and publish them
with an authenticated maintainer account (contracts first). Then register each
package using npm 11.15.0 or later with account 2FA enabled:
npm trust github @nextlevelbuilder/contracts --repo nextlevelbuilder/nlb-directory-toolkits --file release.yml --allow-publish --yes
npm trust github @nextlevelbuilder/cli --repo nextlevelbuilder/nlb-directory-toolkits --file release.yml --allow-publish --yes
npm trust github @nextlevelbuilder/mcp --repo nextlevelbuilder/nlb-directory-toolkits --file release.yml --allow-publish --yesPublish subsequent versions through tags and verify the workflow, registry versions and provenance before calling the release complete. If a release partly publishes, inspect the registry before retrying: npm versions are immutable. See npm trusted publishing and npm trust for account setup.