Skip to content
TrustedSkillsbeta
Back to all skills

Feature Analyzer

Checked
notedit·vlatest·other·MIT

This tool dissects text to identify key features and patterns, streamlining content analysis & research.

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 notedit/happy-skills --skill feature-analyzer -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

notedit

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 notedit/happy-skills at 9a2d593b62.

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

Commit
9a2d593b62
Manifest
skills/dev/feature-analyzer/SKILL.md
Scanned
1 file, 347 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 Feature Analyzer skill assists in designing new features and specifications by systematically gathering information and validating ideas. It begins by exploring existing codebases to understand project structure, conventions, and related components. Crucially, it uses a structured questioning process ("AskUserQuestion") to efficiently collect requirements from users, breaking down the process into focused rounds of questions.

When to use it

  • When designing a new feature or enhancement for an existing system.
  • To clarify the scope and goals of a development task before implementation.
  • To ensure alignment with project conventions and related features.
  • During initial planning phases when requirements are unclear and need exploration.

Key capabilities

  • Codebase Exploration: Analyzes code to understand project structure, tech stack, and existing patterns.
  • Structured Questioning (AskUserQuestion): Collects information through a series of predefined questions in batches.
  • Requirement Round Management: Organizes questioning into rounds focused on core requirements and technical details.
  • Multi-Select Options: Allows for selecting multiple options when answering questions, providing more nuanced input.

Example prompts

  • "Let's design a new user authentication feature. I’m using the feature-analyzer skill to design this feature."
  • “I need help defining the scope of a new reporting module. Can you use Feature Analyzer to guide me through the process?”
  • "Can you analyze our codebase and then ask me questions about a proposed API endpoint?"

Tips & gotchas

  • The skill announces its usage at the start ("I'm using the feature-analyzer skill...").
  • It utilizes "AskUserQuestion" for efficient data collection; be prepared to answer the presented questions.
  • The questioning process is structured into rounds, so expect a series of prompts related to goals and technical details.