Skip to content
SlashClone

Docs

Reading a kit page

What each part of a kit page tells you, so you can decide whether a kit is right for you before you use it.

A kit page tells you what the kit makes, what it needs from you, and what it can touch. Read those three parts before you add anything.

What it makes

What it makes shows a sample request under You ask, and what the kit made from it. Every result has a label that says where it came from:

  • Verified run. SlashClone gave Claude the kit's instructions and a sample request in a locked-down sandbox, and kept what it made.
  • Creator's example. The kit's maker made this with it and shared it.
  • Sample run. SlashClone ran the kit's own test on the maker's sample, and it passed.
  • From the community. Someone who used the kit shared what it made.

Will this work for me?

This panel sits under the main button.

  • Effort says how much setup to expect, from Works out of the box to For builders.
  • Works in says where it runs. Some kits work only in Claude Code.
  • You need lists the plan, accounts, connectors, programs, and keys it needs. Click an item to see what it is and where to get it. Keys and accounts a kit needs has more.

The Safety label

Beside it, the Safety label sums up the kit.

  • Who made it. The SlashClone house account, a verified organization or person, or someone not verified, with how old the account is.
  • What it touches. The files it reads and writes, the sites it connects to, the commands it runs, and any hooks. Hooks run without asking, so they get a warning mark, as do commands that install other software.
  • Scan. The result of the automatic check.
  • Signed. "Files match what was published" means you get the files that were checked. It is not a review.

What it can access has the full list. These are the kit's permissions. Claude Code turns them into rules and asks you before anything not on the list. Other tools do not hold a kit to its list. A kit that tidies spreadsheets has no reason to read your email.

What the automatic check looks for

Every version of every kit is checked before anyone can add it. The check reads every file, including the words inside Word, Excel, and PowerPoint files, and looks for:

  • keys, passwords, and other secrets left in the files
  • commands that download and run code from elsewhere, delete whole folders, read login files, or send your files away
  • hidden instructions written to turn Claude against what you asked
  • anything the kit does that is not on its list, like a site it did not name
  • a kit made to look like another author's kit

A kit that fails is not published. A kit with warnings is published with a warning mark, and the Safety tab lists each finding.

The check matches patterns in text. It is not a person reading the kit, and it cannot tell you what a kit will do. A command pieced together from parts, or instructions in another language, can slip past it. How SlashClone checks what people share has the whole list, and what we check on project pages and at sign-in.

Some kits also get an AI review, a plain-language summary of what the kit does. When a kit did not get one, the Scan row says so, for example Scanned. Not AI reviewed. That kit was still scanned and signed.

Versions and what changed

Each time the maker changes a kit, they share a new version, and old versions stay exactly as they were. Versions lists them, and What changed compares two. More in Updates and versions.

Official kits

On kit cards, a small check beside the maker's name marks a kit from the SlashClone team or a verified organization. A kit made for a company's product by someone outside that company is labeled Community.

Questions and comments

The Comments tab is where people talk about the kit. Click Ask the maker to ask the people who run it a question, or ask for a change you would like. Comments, questions, and notifications covers how it works.

Report a kit

Use Report this at the bottom of the Safety label, signed in. Reports go to a person on our team. A kit confirmed as malicious is pulled, and everyone who installed it is told. For a copyright problem, use the takedown form.

Your cookie choices

We use cookies you can say no to for analytics, ad measurement, and embedded videos. Signing in works either way. You can change this any time from Cookie settings at the bottom of every page. What we use

Cookies that keep you signed in and remember these choices are always on. Everything else is off until you turn it on.