Skip to content
TrustedSkillsbeta
Back to all skills

Backend Endpoint

Checked
alekspetrov·vlatest·backend·MIT

Connects to and retrieves data from specified backend endpoints via API calls, returning structured results.

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 qf-studio/navigator --skill backend-endpoint -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

alekspetrov

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 alekspetrov/navigator at 4b2ae38d01.

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

Commit
4b2ae38d01
Manifest
skills/backend-endpoint/SKILL.md
Scanned
10 files, 1,234 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 allows AI agents to interact with and retrieve data from backend endpoints. It can execute HTTP requests (GET, POST, PUT, DELETE) against specified URLs, handling authentication where necessary. The agent can then parse the response body and extract relevant information for further processing or use in subsequent actions.

When to use it

  • Data Retrieval: Fetching product details from an e-commerce API based on a user's search query.
  • System Automation: Triggering a build process by sending a POST request to a CI/CD endpoint.
  • Content Updates: Updating records in a database via an API call after receiving new information.
  • Monitoring & Reporting: Regularly querying monitoring endpoints to gather system health data and generate reports.

Key capabilities

  • HTTP Request Execution (GET, POST, PUT, DELETE)
  • Authentication Handling
  • Response Body Parsing
  • URL Specification

Example prompts

  • "Fetch the latest weather forecast from api.example.com/weather."
  • "Send a POST request to https://api.myservice.com/orders with the following data: { 'customer_id': 123, 'items': [...] }."
  • "Update the status of order #456 to 'shipped' using the PUT endpoint at api.example.com/orders/456."

Tips & gotchas

The agent needs access and permissions to the specified backend endpoints. Ensure proper authentication credentials are provided if required by the API.