Skip to content
TrustedSkillsbeta
Back to all skills

Backend Standards

Checked
clarkkkk·vlatest·backend

Enforces consistent backend code style, architecture, and best practices based on Clarkkkk's defined standards for improved maintainability.

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 clarkkkk/seagull --skill backend-standards -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

clarkkkk

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

    Makes no network calls.

    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.

  • 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 clarkkkk/seagull at 802398e838.

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

Commit
802398e838
Manifest
skills/backend-standards/SKILL.md
Scanned
6 files, 525 lines
Copies in repo
3 — all of them scanned
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, backend-standards, provides a set of guidelines and best practices for developing robust and maintainable backend systems. It focuses on ensuring code quality through consistent formatting, linting rules, and adherence to architectural patterns. The skill aims to improve developer productivity and reduce technical debt by enforcing standardized coding conventions.

When to use it

  • New project setup: To establish a baseline of code quality from the beginning.
  • Code reviews: To automatically check for compliance with backend standards during pull requests.
  • Refactoring existing codebase: To gradually align legacy code with modern best practices.
  • Onboarding new developers: To quickly familiarize them with project-specific coding conventions.

Key capabilities

  • Enforces consistent code formatting.
  • Applies linting rules for improved code quality.
  • Promotes adherence to architectural patterns.
  • Provides guidelines for backend development best practices.

Example prompts

  • "Apply the backend standards to this Python file."
  • "Check this JavaScript code for compliance with the backend-standards."
  • "Generate a configuration file based on the backend-standards for a new Node.js project."

Tips & gotchas

The skill requires familiarity with common backend development tools and languages (e.g., Python, JavaScript/Node.js). It's most effective when integrated into an automated build or code review pipeline to ensure continuous compliance.