Skip to content
TrustedSkillsbeta
Back to all skills

Agent Dev Backend Api

Checked
ruvnet·vlatest·backend·MIT

Helps with backend development, API as part of orchestrating AI agents and multi-step workflows workflows.

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 ruvnet/ruflo --skill agent-dev-backend-api --full-depth -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

ruvnet

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 ruvnet/claude-flow at 49da6ecc44.

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

Commit
49da6ecc44
Manifest
.agents/skills/agent-dev-backend-api/SKILL.md
Scanned
1 file, 338 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 access to a backend API specifically designed for developing AI agents. It enables programmatic interaction with agent functionalities, allowing for automation and integration into larger workflows. The API facilitates tasks such as managing agent state, triggering actions, and retrieving data related to agent execution.

When to use it

  • Automating agent deployment and configuration processes.
  • Building custom dashboards or monitoring tools for agents.
  • Integrating agent capabilities with existing backend systems.
  • Creating complex workflows that involve multiple agents interacting with each other.

Key capabilities

  • Programmatic access to agent functionalities
  • Agent state management
  • Action triggering
  • Data retrieval related to agent execution

Example prompts

  • "Trigger the 'summarize_document' action on agent 'research-assistant'."
  • "Retrieve the current state of agent 'customer-support'."
  • "List all available actions for agent 'data-analyst'."

Tips & gotchas

The skill requires a solid understanding of API interactions and potentially authentication mechanisms. Refer to accompanying documentation or examples for specific endpoint details and usage guidelines.