Skip to content
TrustedSkillsbeta
Back to all skills

Requirement Assistant

Checked
asiaostrich·vlatest·other

This Requirement Assistant helps you quickly extract and organize user needs from text, streamlining project planning & ensuring nothing's missed.

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 asiaostrich/universal-dev-standards --skill requirement-assistant --full-depth -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

asiaostrich

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 asiaostrich/universal-dev-standards at 2c7106b0d4.

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

Commit
2c7106b0d4
Manifest
skills/requirement-assistant/SKILL.md
Scanned
12 files, 2,934 lines
Copies in repo
3 — 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

The Requirement Assistant skill helps users generate and refine requirements for software projects. It can take a high-level project description and produce detailed, actionable requirement statements. This includes identifying stakeholders, defining acceptance criteria, and ensuring requirements are testable and traceable.

When to use it

  • Generating initial requirements for a new feature or product.
  • Refining existing requirements to ensure clarity and completeness.
  • Creating user stories from high-level project goals.
  • Identifying potential gaps in requirement documentation.
  • Ensuring alignment between stakeholders and documented needs.

Key capabilities

  • Requirement generation from descriptions
  • Stakeholder identification
  • Acceptance criteria definition
  • Testability assessment
  • Traceability support

Example prompts

  • "Generate requirements for a mobile app that allows users to track their daily water intake."
  • "Refine the following requirement: 'The system should be fast.' Make it more specific and measurable."
  • “Identify stakeholders for a project building an internal knowledge base.”

Tips & gotchas

To get the best results, provide as much context as possible about the project or feature. The assistant is most effective when given clear goals and constraints.