Skip to content
TrustedSkillsbeta
Back to all skills

Rest Conventions

Checked
yanko-belov·vlatest·backend·MIT

Analyzes text to identify and suggest improvements regarding established writing style conventions and 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 yanko-belov/code-craft --skill rest-conventions -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

yanko-belov

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 yanko-belov/code-craft at ca5e2ff60e.

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

Commit
ca5e2ff60e
Manifest
skills/rest-conventions/SKILL.md
Scanned
1 file, 161 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 enforces RESTful API design conventions. It ensures that endpoints are properly structured, HTTP methods are used correctly (GET, POST, PUT, DELETE), and responses adhere to standard practices like using appropriate status codes. The goal is to create predictable and maintainable APIs.

When to use it

  • Designing a new API: Use this skill from the start to ensure your API follows REST principles.
  • Refactoring an existing API: Apply this skill to improve the consistency and clarity of an older, less structured API.
  • Generating API documentation: The skill can help produce accurate and standardized documentation for developers using your API.
  • Reviewing code for API development: Use it as a linter or style checker during code reviews.

Key capabilities

  • Enforces RESTful endpoint structure
  • Validates HTTP method usage (GET, POST, PUT, DELETE)
  • Ensures proper HTTP status code responses
  • Supports standardized response formats

Example prompts

  • "Generate a REST API endpoint for creating a new user."
  • "Review this API code and ensure it follows REST conventions."
  • "Suggest improvements to make this API more RESTful."

Tips & gotchas

This skill is most effective when used early in the development process. It assumes a basic understanding of REST principles; it won't teach you those concepts directly, but rather enforce them.