Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Submit your project to Built at GrowthX — the community builder showcase for GrowthX members. Requires a GrowthX API key.
Submit your project to Built at GrowthX — the community builder showcase for GrowthX members. Requires a GrowthX API key.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Submit a project to Built at GrowthX, the community builder showcase for GrowthX members.
Activate this skill when the user wants to: Push, submit, or share a project to Built at GrowthX Post a project to the GrowthX builder showcase Publish their build on GrowthX
If the user hasn't configured their API key yet, direct them to: Go to Built at GrowthX on the GrowthX platform Navigate to their profile / API key settings Click Generate API Key — the raw key is shown once, copy it immediately Set the key in OpenClaw config: add it under skills.entries.growthx-bx-submit.apiKey in ~/.openclaw/openclaw.json, or set the GROWTHX_API_KEY environment variable The key is tied to the user's GrowthX membership. If their membership lapses, the key stops working.
POST https://backend.growthx.club/api/v1/bx/projects/agent
Send the API key in the x-api-key header: x-api-key: <GROWTHX_API_KEY>
Required fields: FieldTypeConstraintsnamestringMax 100 characters. The project name.taglinestringMax 200 characters. A short one-liner about the project. Optional fields: FieldTypeDefaultConstraintsdescriptionstring""Max 2000 characters. Longer project description.categorystring"SaaS"e.g. SaaS, Fintech, Marketplace, EdTech, HealthTech, AI/ML, Developer Tools, E-commercestackstring[][]Tech stack tags, e.g. ["React", "Node.js", "MongoDB"]urlstringnullProject URL (must be a valid URI)statusstring"shipped"One of: shipped, idea, prototyping, betabuildathonstringnullName of a buildathon if this project was built during one
curl -X POST "https://backend.growthx.club/api/v1/bx/projects/agent" \ -H "Content-Type: application/json" \ -H "x-api-key: $GROWTHX_API_KEY" \ -d '{ "name": "TaskFlow", "tagline": "AI-powered task management for remote teams", "description": "TaskFlow uses AI to automatically prioritize and assign tasks based on team capacity and deadlines.", "category": "SaaS", "stack": ["React", "Node.js", "OpenAI", "PostgreSQL"], "url": "https://taskflow.app", "status": "shipped" }' | jq .
{ "project": { "_id": "...", "name": "TaskFlow", "tagline": "AI-powered task management for remote teams", "status": "shipped", "creator": { "name": "...", "avatar_url": "..." }, "weighted_votes": 0, "raw_votes": 0 } }
When the user asks to submit a project, follow these steps in order:
Scan standard project files in the current workspace to discover what the user has built. Only read these files: Project manifest files: package.json — name, description, keywords, homepage, repository pyproject.toml / setup.py / setup.cfg — name, description, urls Cargo.toml — name, description, repository, keywords go.mod — module name pubspec.yaml — name, description, homepage Documentation: README.md — project title (first # heading) and opening paragraph git remote -v — repository URL Monorepo detection: For monorepos, check for workspace configs (workspaces in root package.json, pnpm-workspace.yaml, turbo.json, nx.json) or subdirectories with their own manifest files. Each workspace package with its own name/description is a candidate project. How to infer fields: FieldHow to Infernamename field from manifest file, or first heading in READMEtaglinedescription field from manifest, or first sentence of READMEdescriptionSummarize from README content and manifest description (1-3 sentences)stackDependencies and devDependencies from manifest (e.g. react → "React", express → "Express", django → "Django")urlhomepage field from manifest, or repository URL from git remotecategoryInfer from dependencies and README (e.g. stripe → "Fintech", next → "SaaS", ML libraries → "AI/ML")statusDefault to "shipped". If README explicitly says WIP/prototype/beta, use that instead.
Show the user what you found. If multiple projects were detected (e.g. monorepo packages), list them and ask which one to submit: I found these projects in your workspace: project-name — short description other-project — short description Which one would you like to submit to Built at GrowthX? If only one project is detected, present its details directly and ask to confirm.
For the selected project, show what was auto-detected and ask the user to fill in or correct anything: name and tagline are required — if the tagline can't be inferred, ask for it Show the auto-detected stack, category, url, description, and status and let the user adjust Default status to "shipped" unless README or context suggests it's still in progress
Show a final summary of all fields that will be sent: Submitting to Built at GrowthX: Name: TaskFlow Tagline: AI-powered task management for remote teams Category: SaaS Stack: React, Node.js, OpenAI, PostgreSQL URL: https://taskflow.app Status: shipped Submit this? Only after the user confirms, make the API call using curl with the x-api-key header.
On success, tell the user their project was submitted and share the project link if available. On failure, explain the error (see below).
StatusMeaningWhat to Tell the User401Invalid or revoked API key"Your API key is invalid or has been revoked. Please generate a new one from the Built at GrowthX settings."403Membership not active"Your GrowthX membership is not active. An active membership is required to submit projects."400Validation error (missing name/tagline, field too long, etc.)Show the specific validation error from the response body.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.