Skip to content
TrustedSkillsbeta
Back to all skills

Shadow Cljs Debug

Checked
riatzukiza·vlatest·testing

Debug shadow-cljs development projects directly within your IDE using this riatzukiza tool for efficient ClojureScript testing.

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 riatzukiza/devel --skill shadow-cljs-debug -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

riatzukiza

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 riatzukiza/devel at 80a95e5638.

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

Commit
80a95e5638
Manifest
.factory/skills/shadow-cljs-debug/SKILL.md
Scanned
2 files, 104 lines
Copies in repo
2 — all of them scanned
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 provides debugging capabilities within Shadow CLJS development environments. It allows developers to inspect and modify application state during runtime, facilitating faster identification and resolution of issues. Specifically, it enables live editing and hot reloading for efficient debugging workflows.

When to use it

  • When encountering unexpected behavior in a ClojureScript application developed with Shadow CLJS.
  • During the development phase to quickly iterate on code changes and observe their effects.
  • To diagnose performance bottlenecks or memory leaks within a Shadow CLJS project.
  • For live debugging of complex interactions between frontend components and backend services.

Key capabilities

  • Live editing of ClojureScript source files.
  • Hot reloading of application updates during development.
  • Runtime inspection of application state.
  • Debugging workflows within the Shadow CLJS environment.

Example prompts

  • "Start debugging my shadow-cljs project."
  • "Inspect the current state of my component at runtime."
  • "Reload the application with my latest code changes."

Tips & gotchas

This skill requires a working Shadow CLJS development environment to be effective. Ensure your project is properly configured for debugging before attempting to use this skill.