Skip to content
TrustedSkillsbeta
Back to all skills

Phoenix Api Channels

Checked
bobmatnyc·vlatest·backend·MIT

Provides API guidance and assistance for agent 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 bobmatnyc/claude-mpm-skills --skill phoenix-api-channels -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

bobmatnyc

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 bobmatnyc/claude-mpm-skills at 718070a7d6.

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

Commit
718070a7d6
Manifest
toolchains/elixir/frameworks/phoenix-api-channels/SKILL.md
Scanned
2 files, 270 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 guidance and assistance for developing APIs using Phoenix, a web framework built on Elixir and the BEAM virtual machine. It enables AI agents to understand and work with Phoenix's features for building REST/JSON APIs and WebSocket Channels, including controllers, contexts (data ownership), PubSub for real-time updates, presence tracking, authentication via plugs, routing, and pipelines. The skill helps developers leverage Phoenix’s architecture for fault tolerance and efficient process management.

When to use it

  • When needing assistance with setting up a new Phoenix API project.
  • For guidance on structuring controllers, contexts, and channels within a Phoenix application.
  • To understand how to implement authentication (session/cookie or token-based) in your APIs.
  • When building real-time features using Channels and PubSub.
  • To troubleshoot routing and pipeline configurations for API versioning.

Key capabilities

  • REST/JSON API Development: Guidance on creating controllers, pipelines, and versioned endpoints.
  • WebSocket Channels & Presence: Support for fan-out real-time updates and user tracking.
  • Authentication: Assistance with session/cookie or token-based authentication using plugs.
  • Contexts & Data Ownership: Understanding how to structure data logic within contexts (using Ecto schemas).
  • Routing and Pipelines: Configuration of API routes, versioning scopes, and request pipelines.

Example prompts

  • "How do I create a new Phoenix project with only the API functionality?"
  • "Can you show me an example of how to implement token-based authentication in a Phoenix controller?"
  • "Explain how PubSub works within a Phoenix Channel."
  • “What is the purpose of the MyApiWeb.Router module?”

Tips & gotchas

  • Keep pipelines short and move authentication/authorization logic into plugs for efficiency.
  • Expose sockets specifically for Channels, restricting transport methods as needed.
  • Controllers should remain thin; delegate data logic to contexts.