agentsclimarketplace

Web backend builder

Skill 0x-Professor/Agent-Skills-Hub/skills/web-backend-builder

Public skill pack for AI coding/automation/penetration-testing agents.

Install
npx -y skills add 0x-Professor/Agent-Skills-Hub --skill web-backend-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scaffold backend API, data models, ORM setup, and endpoint inventory with OpenAPI output.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.5 KB, 264 tokens by cl100k_base, as published. Nobody here has run it

Web Backend Builder

Objective

Scaffold a backend foundation from project-config.json including data model planning, ORM recommendations, API endpoint inventory, and OpenAPI output.

Required Workflow

  1. Read project-config.json.
  2. Scaffold the selected backend framework (FastAPI, Express, Django, Gin, and other configured options).
  3. Define data models from project type and ask for missing entities when unclear.
  4. Configure ORM/query layer guidance:
    • Prisma (Node.js)
    • Drizzle ORM (TypeScript)
    • SQLAlchemy (FastAPI/Python)
    • Mongoose (MongoDB)
  5. Scaffold CRUD endpoints, auth middleware, and file upload handlers.
  6. If Supabase is selected, include @supabase/supabase-js, RLS policy planning, and Edge Function notes.
  7. Enforce environment variable setup with .env.example and no committed secrets.
  8. Generate openapi.yaml covering all endpoints.
  9. Output backend scaffold artifacts, openapi.yaml, and backend-report.json.

Execution

python skills/web-backend-builder/scripts/backend_builder.py --input <workspace> --output <out.json> --format json

References

  • references/tools.md

Gives 0 of the 12 instructions most project setup skills give in 264 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07

  • ask one question at a timein 29 of 999, across 28 files
  • detect the package manager from lockfilesin 28 of 999, across 9 files
  • present findings to the userin 26 of 999, across 5 files
  • explore current repo statein 24 of 999, across 3 files
  • update the agent skills block in place if it existsin 24 of 999, across 3 files
  • install husky lint-staged and prettierin 23 of 999, across 4 files
  • create the lintstagedrc filein 22 of 999, across 3 files
  • commit all changed filesin 22 of 999, across 3 files
  • run lint-staged to verify it worksin 22 of 999, across 3 files
  • create the husky pre-commit filein 21 of 999, across 2 files
  • create a prettierrc file if missingin 21 of 999, across 2 files
  • initialize huskyin 21 of 999, across 2 files

Said here and by no other author read

  • read project-config.json
  • scaffold the selected backend framework
  • define data models from project type
  • ask for missing entities when unclear
  • configure ORM or query layer guidance
  • scaffold CRUD endpoints, auth middleware, and file upload handlers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.