Skip to content
TrustedSkillsbeta
Back to all skills

Intent Check

Checked
arcblock·vlatest·security·MIT

This Intent Check skill verifies if a user’s query aligns with the expected business intent, ensuring accurate and relevant bot responses for improved user experiences.

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 arcblock/idd --skill intent-check -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

arcblock

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 arcblock/idd at d46fc54044.

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

Scanned
1 file, 173 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

intent-check

What it does

This skill enables AI agents to validate user input against predefined rules or conditions before executing actions. It acts as a gatekeeper, ensuring that requests meet specific criteria for safety, authorization, or data integrity.

When to use it

  • Preventing unauthorized access by verifying user roles or permissions before granting entry to sensitive systems.
  • Sanitizing incoming data to ensure it matches expected formats, such as validating email addresses or phone numbers.
  • Blocking malicious inputs like SQL injection attempts or script tags in chat interfaces.
  • Enforcing business logic constraints, such as ensuring a user has sufficient balance before processing a transaction.

Key capabilities

  • Rule-based validation of incoming prompts and data payloads.
  • Conditional execution flow based on input compliance.
  • Error handling for inputs that fail defined checks.

Example prompts

  • "Check if my request to access the admin dashboard complies with my current user role."
  • "Validate this customer email address before adding them to the newsletter list."
  • "Run an intent check on this transaction request to ensure the amount is within the daily limit."

Tips & gotchas

Ensure your predefined rules are comprehensive enough to catch edge cases but flexible enough to avoid false positives. Regularly update validation logic as application requirements evolve to maintain security and usability.