Skip to content
TrustedSkillsbeta
Back to all skills

Spec Shaping

Checked
nweii·vlatest·writing·MIT

Spec Shaping helps refine detailed specifications by iteratively generating variations based on provided constraints – boosting clarity and accuracy.

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 nweii/agent-stuff --skill spec-shaping -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

nweii

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 nweii/agent-stuff at 5854362cce.

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

Commit
5854362cce
Manifest
skills/spec-shaping/SKILL.md
Scanned
1 file, 134 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

The spec-shaping skill allows an AI agent to refine and improve existing specifications or instructions. It can take a rough draft of a specification, identify areas for clarity or completeness, and suggest improvements based on best practices. The goal is to produce well-defined, actionable specifications that lead to better outcomes.

When to use it

  • Improving initial drafts: Use when you have a preliminary specification but suspect it's unclear or incomplete.
  • Refining complex instructions: Apply when providing detailed instructions for tasks where precision is critical.
  • Standardizing specifications: Leverage this skill to ensure consistency across multiple specifications within a project.
  • Automating documentation updates: Integrate into workflows to automatically improve the quality of technical documentation.

Key capabilities

  • Identifies areas needing clarification in existing specifications.
  • Suggests improvements for completeness and accuracy.
  • Refines language for better readability and actionability.
  • Supports best practices for specification writing.

Example prompts

  • "Please review this product specification and suggest ways to improve its clarity: [paste specification here]"
  • "Can you refine these instructions for a software development task, ensuring they are actionable? [paste instructions here]"
  • "I have a draft of an API specification; can you identify any missing details or areas that need more definition?"

Tips & gotchas

The quality of the output depends heavily on the initial specification provided. A poorly written or ambiguous starting point will likely result in less effective refinements.