growthx-bx-submit_skill

This skill submits your GrowthX project to Built at GrowthX using your GrowthX API key and auto-filled project details.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill growthx-bx-submit

  • _meta.json288 B
  • SKILL.md6.7 KB

Overview

This skill submits your project to Built at GrowthX, the community builder showcase for GrowthX members. It requires a GrowthX API key and automates discovery of project metadata from the current workspace. The skill helps you review, edit, and confirm fields before sending the project to the GrowthX API.

How this skill works

The skill scans common manifest and documentation files in the workspace (package.json, pyproject.toml, README.md, git remotes, etc.) to infer name, tagline, description, stack, URL, category, and status. It lists detected projects (supports monorepos), prompts you to fill or correct required fields, and then submits the final payload to the GrowthX endpoint using your x-api-key header. On success it reports the created project; on failure it surfaces API validation and auth errors with actionable messages.

When to use it

  • You want to publish a finished project to the Built at GrowthX showcase.
  • You need to submit one package from a monorepo and want automatic metadata extraction.
  • You want a quick flow to create or update a GrowthX project entry without manual API calls.
  • You need to validate project fields against GrowthX constraints before submission.

Best practices

  • Provide a concise tagline (<= 200 characters) — it is required and shown prominently.
  • Keep the README top paragraph focused; the skill summarizes it into the description.
  • Set your project homepage or repository URL in manifest files so the URL is inferred.
  • Verify the inferred tech stack and category; adjust if inference mistakes occur.
  • Store your API key securely (environment variable GROWTHX_API_KEY or config entry).

Example use cases

  • Submit a newly shipped web app found via package.json and README.md.
  • Choose a specific workspace package from a monorepo and publish only that package.
  • Fill in a missing tagline the skill could not infer, then confirm and submit.
  • Detect project stack from dependencies and include it in the submission for discoverability.

FAQ

A 401 response is returned. Generate a new key from Built at GrowthX settings and update your environment or config.

Can the skill handle monorepos?

Yes. It detects workspace packages with their own manifests and lets you pick which package to submit.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational