Skip to content
TrustedSkillsbeta
Back to all skills

Chatkit Backend

Checked
maneeshanif·vlatest·backend

Provides robust API endpoints for chat history management, user authentication, and message processing within a chatbot application.

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 maneeshanif/todo-spec-driven --skill chatkit-backend -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

maneeshanif

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 maneeshanif/todo-spec-driven at c76f22dd44.

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

Commit
c76f22dd44
Manifest
.claude/skills/chatkit-backend/SKILL.md
Scanned
3 files, 1,671 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

The chatkit-backend skill provides a backend for chat applications. It enables features like user authentication, message persistence, and real-time communication capabilities. This allows AI agents to power interactive chat experiences with users.

When to use it

  • Building a customer support chatbot that needs to authenticate users and store conversation history.
  • Creating a collaborative messaging application where multiple users can interact in real-time.
  • Developing an internal knowledge base accessible via chat, requiring user accounts and message tracking.
  • Implementing a community forum with chat functionality needing secure user management.

Key capabilities

  • User authentication
  • Message persistence
  • Real-time communication

Example prompts

  • "Authenticate the user 'john.doe' and grant them access to the chat."
  • "Store this message from user 'jane.smith' in the database: 'Hello, how can I help?'"
  • "Send a notification to all connected users that a new message has arrived."

Tips & gotchas

The backend requires proper configuration of authentication credentials and database connections for optimal performance. Ensure your AI agent is authorized to access these resources.