New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Manage Backend Layers

by baserow in baserow/baserow

Manage Baserow backend feature layers across Django models, handlers, services, undoable actions, serializers, API views, URLs, permissions, signals, migrations, and tests.

Custom licenceAuto-check passedBackend & APIs

Install Manage Backend Layers

skills CLI
$ npx skills add baserow/baserow --skill manage-backend-layers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install baserow/baserow manage-backend-layers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/manage-backend-layers .claude/skills/manage-backend-layers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
manage-backend-layers
GitHub stars
6.1k
Token cost
~2.4k tokens
SKILL.md length
1,078 words
Files
2
Skills in repo
11
Repo updated
First seen
Licence
Custom licence

At a glance

Manage Baserow backend feature layers across Django models, handlers, services, undoable actions, serializers, API views, URLs, permissions, signals, migrations, and tests.

  • Works in 4 steps: Is this a new model-backed concept, or a… → Is the behavior pure domain persistence,… → Does it need permissions, workspace… → …
  • Changing backend CRUD/domain behavior that spans model
  • SKILL.md covers First Step, Layer Responsibilities, Implementation Order and Permission And Signal Pattern, plus 2 more sections
  • Calls just and rg

What it does

Manage Backend Layers is an agent skill from baserow/baserow. Manage Baserow backend feature layers across Django models, handlers, services, undoable actions, serializers, API views, URLs, permissions, signals, migrations, and tests. Use when adding or changing backend CRUD/domain behavior that spans model, handler, service, action, and view layers; use the automation modules as the preferred modern pattern.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Backend & APIs, covering Backend development. It works with Django and Airtable. The repository describes itself as: Build databases, automations, apps & agents with AI — no code. Open source platform available on cloud and self-hosted. GDPR, HIPAA, SOC 2 compliant. Best Airtable alternative.

When your agent uses it

  • Changing backend CRUD/domain behavior that spans model
  • Use the automation modules as the preferred modern pattern

Example prompts

  • “/manage-backend-layers”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Is this a new model-backed concept, or a change to an existing model?
  2. Is the behavior pure domain persistence, user-facing mutation, undoable, API-exposed, or all of those?
  3. Does it need permissions, workspace scoping, signals, trash, import/export, ordering, or specific typed subclasses?
  4. Is there a close automation workflow/node pattern, or a closer pattern in the target app?

What it can do on your machine

Read from SKILL.md and the folder at commit 674e4b1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • just
    • rg

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Manage Backend Layers loads about 2.4k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 1,078 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,078 words (~2,393 tokens).

“Use this skill when a backend change spans several Baserow layers, especially:”

— opening of SKILL.md by baserow, Custom licence
name
manage-backend-layers

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .agents/skills/manage-backend-layers of baserow/baserow.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 674e4b1

Compare with similar skills

Manage Backend Layers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Manage Backend Layers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Manage Backend Layers this skillbaserow/baserow6.1k—~2.4kAutomated safety check: PassCustom licence
Saleor Django Schema Migrationsaleor/saleor23k—~1kAutomated safety check: PassBSD-3-Clause
Django Access Reviewgetsentry/skills1k3 repos~2.6kAutomated safety check: NotesApache-2.0
Arch Wikiahmedemad3/arch-wiki250—~5.1kAutomated safety check: PassNone
Run Testsnetboxlabs/netbox-branching155—~1.2kAutomated safety check: PassCustom licence
Add Management Commandaropan/clist439—~848Automated safety check: PassApache-2.0

Similar skills

  • Saleor Django Schema Migration

    saleor/saleor

    Generates and splits Django schema migrations for Saleor with manage.py makemigrations, enforcing one new model or one field change per migration file.

    23k GitHub stars~1k tokensUpdated today
    Backend & APIsAuto-check passed

  • Django Access Review

    getsentry/skills

    Official

    Django access control and IDOR security review. An agent skill from getsentry/skills.

    1k GitHub starsUsed in 3 repos~2.6k tokens
    Backend & APIsAuto-check: notes

  • Arch Wiki

    ahmedemad3/arch-wiki

    Scans any project codebase for new/changed modules, endpoints, middleware, infrastructure, Docker topologies, SQL queries, or permissions and updates docs/architecture/architecture.json.

    250 GitHub stars~5.1k tokensUpdated 20 days ago
    Backend & APIsAuto-check passed

  • Run Tests

    netboxlabs/netbox-branching

    Run the netboxbranching plugin's Django test suite against a local NetBox checkout.

    155 GitHub stars~1.2k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Add Management Command

    aropan/clist

    Add or change a CLIST Django management command, including arguments, resource selection, EventLog monitoring, or cron and Healthchecks wiring.

    439 GitHub stars~848 tokensUpdated 5 days ago
    Backend & APIsAuto-check passed

  • Django Run Locally

    fossasia/eventyay

    Steps for initiating the Django development server without Docker

    1.7k GitHub stars~411 tokensUpdated today
    Backend & APIsAuto-check passed

More from baserow/baserow

All 11 skills in this repo

  • Review PR

    baserow/baserow

    Review a Baserow pull request, branch, or diff against its actual base the way the maintainers do.

    6.1k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Add Config Env Var

    baserow/baserow

    Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…

    6.1k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Create Changelog

    baserow/baserow

    Generate a changelog entry for the current Git branch by inspecting changed files, classifying the domain and type, writing a short public-friendly message, and running just changelog add after the…

    6.1k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Silk Profiler

    baserow/baserow

    Investigate backend performance using Django Silk profiling data.

    6.1k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Baserow Registry

    baserow/baserow

    Explain, create, update, or use Baserow registries across backend and frontend code, including Instance/Registry patterns, registration points, model-backed type registries, serializer/API…

    6.1k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Core Graph

    baserow/baserow

    A skill your agent uses when working on code involving Element/Page relationships in the Application Builder (contrib/builder) or AutomationNode/AutomationWorkflow relationships in the Automation…

    6.1k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Manage Backend Layers

What does Manage Backend Layers do?

Manage Baserow backend feature layers across Django models, handlers, services, undoable actions, serializers, API views, URLs, permissions, signals, migrations, and tests. Manage Backend Layers is an agent skill from baserow/baserow. Manage Baserow backend feature layers across Django models, handlers, services, undoable actions, serializers, API views, URLs, permissions, signals, migrations, and tests.

When should I use Manage Backend Layers?

Manage Backend Layers fits situations like: changing backend CRUD/domain behavior that spans model; use the automation modules as the preferred modern pattern.

How do I install Manage Backend Layers in Claude Code?

Run `npx skills add baserow/baserow --skill manage-backend-layers -a claude-code`. Or copy the skill folder (.agents/skills/manage-backend-layers in baserow/baserow) into .claude/skills/manage-backend-layers in your project. Claude Code loads it when a task matches its description.

How do I install Manage Backend Layers in Codex?

Run `npx skills add baserow/baserow --skill manage-backend-layers -a codex`. Or copy the skill folder (.agents/skills/manage-backend-layers in baserow/baserow) into .agents/skills/manage-backend-layers in your project. Codex loads it when a task matches its description.

Can I use Manage Backend Layers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add baserow/baserow --skill manage-backend-layers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manage-backend-layers, .gemini/skills/manage-backend-layers, .github/skills/manage-backend-layers and .opencode/skills/manage-backend-layers in your project.

What does Manage Backend Layers need to run?

Going by SKILL.md and its folder, Manage Backend Layers needs the command-line tools its instructions call (just and rg).

Does Manage Backend Layers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Manage Backend Layers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Manage Backend Layers use?

Manage Backend Layers has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Manage Backend Layers use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Manage Backend Layers?

Skills that share tags, products or a category with Manage Backend Layers: Saleor Django Schema Migration (saleor/saleor, 23k stars), Django Access Review (getsentry/skills, 1k stars), Arch Wiki (ahmedemad3/arch-wiki, 250 stars) and Run Tests (netboxlabs/netbox-branching, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Manage Backend Layers?

baserow (a GitHub organization) maintains it in baserow/baserow, which has 6,103 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 9, 2026.

Source: baserow/baserow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.