Skip to content
TrustedSkillsbeta
Back to all skills

Pocketbase Best Practices

Checked
greendesertsnow·vlatest·backend·MIT

Ensures PocketBase databases adhere to greendesertsnow's recommended security, performance, and scalability best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add greendesertsnow/pocketbase-skills --skill pocketbase-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

greendesertsnow

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: 127.0.0.1.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    127.0.0.1local

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned greendesertsnow/pocketbase-skills at 6565fa03a8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6565fa03a8
Manifest
skills/pocketbase-best-practices/SKILL.md
Scanned
60 files, 13,005 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides a curated set of best practices for configuring and securing PocketBase instances, ensuring reliable backend performance. It guides users through optimizing database schemas, managing authentication flows, and hardening API endpoints against common vulnerabilities.

When to use it

  • You are setting up a new PocketBase instance and need a secure baseline configuration immediately.
  • Your application is experiencing latency issues due to inefficient database queries or unoptimized collections.
  • You require guidance on implementing role-based access control (RBAC) for multi-tenant SaaS applications.
  • You need to audit your current setup against industry standards for data privacy and API security.

Key capabilities

  • Database schema optimization strategies for high-throughput workloads.
  • Authentication and authorization configuration patterns.
  • API security hardening techniques including rate limiting and CORS management.
  • Collection field type selection guidelines based on data integrity needs.

Example prompts

  • "Generate a secure PocketBase initialization script with default collections configured for user authentication."
  • "List the top five security misconfigurations to avoid when deploying PocketBase in production."
  • "Explain how to structure collection rules to enforce strict read/write permissions between different user roles."

Tips & gotchas

Ensure you have a basic understanding of Go and RESTful APIs, as PocketBase is built on these technologies. While this skill covers best practices, always test your configurations in a staging environment before applying them to production data to prevent accidental lockouts or data loss.