Mocking Assistant
CheckedThis "Mocking Assistant" generates playful, sarcastic responses for creative roleplay and humorous interactions – perfect for adding wit!
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add patricio0312rev/skills --skill mocking-assistant -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
patricio0312rev
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.
Automated safety checks
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 patricio0312rev/skills at 79ea6af485.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 79ea6af485
- Scanned
- 1 file, 366 lines
About this skill
What it does
This Mocking Assistant skill enables AI agents to generate reliable mocks for APIs and services, primarily used within testing environments. It leverages MSW (Mock Service Worker) to intercept API requests and return predefined responses, allowing developers to isolate components during testing without relying on actual backend servers. The assistant provides examples of how to set up handlers, fixtures, and test-specific mocks using the MSW framework.
When to use it
- Isolating UI Components: Test a user interface component in isolation by mocking the API calls it makes.
- Simulating Error Conditions: Create mock responses that simulate server errors (e.g., 404 Not Found) for testing error handling logic.
- Controlling Response Data: Define specific data payloads to be returned by an API endpoint, enabling predictable test scenarios.
- Testing Slow Network Conditions: Simulate slow network response times using delayed responses in mocks.
Key capabilities
- API Endpoint Mocking: Create mock handlers for GET and POST requests.
- Response Customization: Define custom JSON payloads for mocked API responses.
- Error Response Simulation: Generate HTTP error responses (e.g., 404).
- Delayed Responses: Introduce artificial delays in response times.
- Fixture Management: Utilize predefined data fixtures to populate mock responses with consistent data.
Example prompts
- "Generate a MSW handler for the
/api/users/:idendpoint that returns user data." - "Create a mock API response for
/api/products/:idthat simulates a 404 error." - "Show me how to set up a delayed response for the
/api/slow-endpointusing MSW."
Tips & gotchas
- This skill assumes familiarity with the MSW framework and its configuration.
- The generated code snippets are intended as starting points and may require adjustments based on your specific project setup.
- Ensure that the necessary dependencies (msw, vitest) are installed in your testing environment.