Skip to content
TrustedSkillsbeta
Back to all skills

Create Specs

Checked
jschulte·vlatest·writing·MIT

Generates detailed technical specifications from high-level project descriptions, saving time and ensuring clarity.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it editor-rescue, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add jschulte/claude-plugins --skill editor-rescue -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

jschulte

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 jschulte/claude-plugins at a6b9f8926d.

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

Commit
a6b9f8926d
Manifest
stackshift/skills/create-specs/SKILL.md
Scanned
5 files, 669 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 generates software specifications based on user input. It can take a description of desired functionality and produce structured specification documents, including details like inputs, outputs, error handling, and edge cases. The resulting specs are intended to be used for development teams building software applications.

When to use it

  • Rapid Prototyping: Quickly generate initial specifications for new features or products before detailed design work begins.
  • Documentation Generation: Automatically create documentation from existing feature descriptions or user stories.
  • Bridging the Gap: Translate high-level requirements into more concrete technical specifications for developers.
  • Standardization: Enforce consistent specification formats across projects and teams.

Key capabilities

  • Generates software specifications
  • Creates structured documents
  • Includes details on inputs, outputs, error handling, and edge cases

Example prompts

  • "Create a spec for an API endpoint that allows users to upload profile pictures."
  • "Generate a specification document describing the functionality of a shopping cart system."
  • “Write specifications for a function that calculates shipping costs based on weight and destination.”

Tips & gotchas

The quality of the generated specs depends heavily on the clarity and detail provided in the initial prompt. Providing sufficient context will yield more useful results.