Skip to content
TrustedSkillsbeta
Back to all skills

Effect Testing Mocking

Checked
mepuka·vlatest·testing·MIT

Simulates external system responses to verify AI agent actions without real dependencies, ensuring reliable behavior.

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 mepuka/effect-ontology --skill effect-testing-mocking -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

mepuka

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 mepuka/effect-ontology at c148102d57.

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

Commit
c148102d57
Manifest
.claude/skills/effect-testing-mocking/SKILL.md
Scanned
1 file, 110 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 allows AI agents to simulate and test the effects of actions in a controlled environment. It facilitates mocking dependencies, enabling isolated testing of specific functionalities without relying on external systems or real-world consequences. This is particularly useful for verifying complex interactions and ensuring predictable behavior within an agent's decision-making process.

When to use it

  • Testing complex workflows: Verify the sequence of actions in a multi-step task, like ordering food online, by mocking payment processing and inventory updates.
  • Simulating edge cases: Test how an agent reacts to unexpected situations or errors by creating mock environments that trigger specific failure conditions.
  • Validating decision logic: Ensure an agent makes the correct choices in various scenarios by controlling the inputs and observing the resulting actions through mocked dependencies.
  • Developing new features: Safely experiment with new functionalities without impacting live systems, using mocks to represent external services or data sources.

Key capabilities

  • Dependency mocking
  • Controlled environment simulation
  • Isolated testing of agent actions
  • Verification of complex interactions

Example prompts

  • "Simulate a scenario where the payment processor returns an error."
  • "Mock the inventory service to report that an item is out of stock."
  • "Test the ordering workflow with a simulated user profile and limited budget."

Tips & gotchas

This skill requires a foundational understanding of software testing principles and mocking techniques. Be sure to clearly define the scope of your mock environment to avoid unintended side effects during testing.