Skip to content
TrustedSkillsbeta
Back to all skills

Ce Auth

Checked
commercengine·vlatest·security

Securely authenticates commercial engine users and transactions via customizable rules and multi-factor authentication.

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 commercengine/skills --skill ce-auth -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

commercengine

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 commercengine/skills at 0916932dba.

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

Commit
0916932dba
Manifest
skills/auth/SKILL.md
Scanned
3 files, 244 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 ce-auth skill provides authentication capabilities to AI agents. It allows secure access and verification of users or systems interacting with applications or services. This ensures only authorized entities can perform specific actions, enhancing security and data integrity within the agent's operational environment.

When to use it

  • Secure API Access: Restrict access to internal APIs based on user roles or credentials.
  • Controlled Resource Usage: Limit resource consumption by authenticated users only.
  • Data Protection: Protect sensitive data from unauthorized access and modification.
  • Workflow Authorization: Control which steps in a workflow can be executed by specific agents or users.

Key capabilities

  • Authentication
  • Authorization
  • Secure Access Verification

Example prompts

  • "Authenticate user 'john.doe' with password 'password123'."
  • "Verify if agent 'agent-42' has permission to access resource '/data/sensitive'."
  • "Grant role 'administrator' to user 'jane.smith'."

Tips & gotchas

The skill requires proper configuration of authentication methods and authorization rules within the environment it operates. Ensure that credentials are handled securely and not exposed in prompts or logs.