NLB Submit (nlb-submit)

Autonomous AgentSkill for scanning a codebase, structuring a rich ProductDocument with 17 block types, computing canonical SHA-256 hashes, and submitting the listing to the Next Level Builders Directory (https://nextlevelbuilder.io or https://staging.nextlevelbuilder.io).

Workflow

[1. Scan Repo] -> [2. Select Template] -> [3. Author product.json] -> [4. Validate & Hash] -> [5. Preview] -> [6. Submit & Activate]

1. Scan Repository

Analyze the current repository to extract metadata:

• Project Name & Slug: From package.json (name), Cargo.toml, pyproject.toml, or folder name.
• Tagline & Description: From README.md header or package.json description.
• Tech Stack: Inspect dependencies, framework configs (next.config, vite.config, drizzle.config), and runtime.
• Repository URL: Git remote URL (git remote get-url origin).
• Website URL: From package.json homepage or production URL.
• Visuals / Screenshots: Look for images in docs/, public/, or screenshots/.

2. Select a Layout Template

Choose one of the 5 pre-configured layout templates based on project type:

Template	Slug	Best For	Included Blocks
Developer Framework & CLI	dev-tool	CLIs, terminal tools, developer packages	hero, techStack, grid, changelog, cta
AI Tool & Autonomous Agent	ai-agent	AI agents, LLMs, MCP servers	hero, mediaGallery, grid, milestones, cta
SaaS Launch	saas-launch	Commercial apps, web platforms, micro-SaaS	hero, mediaGallery, grid, techStack, faq, cta
Curated Community / Directory	community-curated	Communities, learning hubs, curated catalogs	hero, founder, grid, cta
Minimalist Showcase	minimalist	Single-fold portfolios, focused tools	hero, mediaGallery, cta

Generate a starter template:

npx @nextlevelbuilder/cli template dev-tool --out product.json

3. Author product.json

Fill out the document using the 17 supported block schemas from @nextlevelbuilder/contracts (every block requires id and props):

1. hero — Headline, subheadline, primary CTA button, badge.
2. carousel — Multi-slide showcase with titles and image URLs.
3. mediaGallery — Multi-image gallery with aspect ratio and captions.
4. quote — Testimonial quote, author, title, avatar URL.
5. grid — Feature and capability cards (1-3 columns).
6. changelog — Version history and release entries.
7. roadmap — Planned, in-progress, and completed milestones.
8. pricing — Tiers with feature lists, pricing, and CTA links.
9. faq — Accordion-style Q&A items.
10. techStack — Categorized technology badges and icons.
11. liveDemo — Embedded sandbox (iframe, height, sandboxTokens).
12. cta — Call-to-action banner with primary action.
13. founder — Founder profile with bio, avatar, and social links.
14. verification — Cryptographic or domain provenance verification.
15. milestones — Timeline of key achievements.
16. caseStudy — Customer story with problem, solution, and outcome metrics.
17. analytics — Real traffic for the NLB-hosted product page. Props: title (1–100 characters; default Traffic), period (7d, 30d, 90d; default 30d). Publishing this block opts into public aggregate totals and daily series; add it only when the owner wants to publish those stats. Do not invent counts or set a product ID. Insert it in the document and use the normal revision submission flow.

Owners can query detailed traffic with nlb traffic <slug> --json or MCP get_product_traffic. Both use existing API credentials. Optional from/to UTC ISO timestamps select an increasing range of at most 90 days ending no later than now; the default is the last 30 days. Visitor counts measure daily sessions: identifiers reset each UTC day, so a returning session on the next day counts again. Referrers, countries, and devices remain organization-authorized even when an Analytics block is published.

4. Validate & Compute Canonical Hash

Validate schema and compute deterministic SHA-256 hash:

# Via CLI:
npx @nextlevelbuilder/cli validate product.json

# Via MCP Tool:
validate_listing(document={ ... })

5. Preview Terminal Box Art

Render ASCII/Unicode box preview in stdout:

npx @nextlevelbuilder/cli preview product.json

6. Submit & Activate

Submit the revision into the moderation review queue. Note: Supply your organization UUID from https://nextlevelbuilder.io/studio:

# Via CLI:
npx @nextlevelbuilder/cli submit product.json --org <ORG_UUID> --api-key <YOUR_KEY>

# For staging environment:
npx @nextlevelbuilder/cli submit product.json --org <ORG_UUID> --api-key <YOUR_KEY> --url https://staging.nextlevelbuilder.io

# Simulate with dry-run:
npx @nextlevelbuilder/cli submit product.json --dry-run

Polar Payment Handling: If your organization does not yet possess an active directory publishing slot entitlement, the submission response returns a direct Polar checkout session URL:

⚠ Payment Required to Activate Directory Listing Slot
• Amount:       $24.50 (Early Bird Slot)
• Checkout URL: https://polar.sh/checkout/...
• Complete checkout above to activate your listing in the review queue.

After completing payment via the Polar checkout URL, run npx @nextlevelbuilder/cli submit product.json --org <ORG_UUID> again to submit your revision into the moderation review queue.

Export AI-optimized Markdown for any published product:

npx @nextlevelbuilder/cli get <your-product-slug> --markdown

Security & Authenticity Invariants

• Deterministic hashing sorts all keys alphabetically and computes consistent canonical SHA-256 digests.
• Submissions are cryptographically anchored by contentHash.
• Organization ownership is strictly validated anti-IDOR via orgId.
• Never commit or log API keys. Use NLB_API_KEY environment variable or --api-key.