Gather requirements by asking clarifying questions until the problem is fully understood.

AGPL-3.0Auto-check passedAgent Workflows

Install Analyze

skills CLI
$ npx skills add hardisgroupcom/sfdx-hardis --skill analyze -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hardisgroupcom/sfdx-hardis analyze --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/analyze .claude/skills/analyze && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analyze
GitHub stars
400
Token cost
~484 tokens
SKILL.md length
224 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Gather requirements by asking clarifying questions until the problem is fully understood.

  • Works in 4 steps: Read context: Look at relevant source… → Ask questions about → Iterate: Keep asking until you are… → …
  • Tasks that involve Requirements gathering
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Analyze is an agent skill from hardisgroupcom/sfdx-hardis. Gather requirements by asking clarifying questions until the problem is fully understood. First step of the contribution workflow.

Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Requirements gathering. It works with Visual Studio Code and Salesforce. The repository describes itself as: French-army-knife Toolbox for Salesforce. Orchestrates base commands and assist users with interactive wizards to make much more than native Salesforce CLI + Allows you to define…. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Requirements gathering

Example prompts

  • “/analyze”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebSearch, WebFetch, AskUserQuestion

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read context: Look at relevant source files, existing patterns, and related commands to understand the current state.
  2. Ask questions about
  3. Iterate: Keep asking until you are confident you understand the full scope.
  4. Summarize your understanding

What it can do on your machine

Read from SKILL.md and the folder at commit 971ac89. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebSearch
    • WebFetch
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Analyze loads about 484 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 224 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~484

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hardisgroupcom/sfdx-hardis at commit 971ac89, republished under its AGPL-3.0 licence (© hardisgroupcom). 224 words, ~484 tokens.

Download SKILL.mdSave it as .claude/skills/analyze/SKILL.md (or your agent's skills folder).
name
analyze
description
Gather requirements by asking clarifying questions until the problem is fully understood. First step of the contribution workflow.
allowed-tools
Read, Glob, Grep, WebSearch, WebFetch, AskUserQuestion
argument-hint
[description of the change]
model
opus

You are a requirements analyst for the sfdx-hardis project.

Your goal is to fully understand what the user wants before any design or implementation begins.

Related agent: this skill mirrors the analyze subagent (same requirements-gathering process, also on Sonnet). The skill stays inline here because it is interactive - it asks the user clarifying questions and iterates with them, which a forked subagent cannot do.

Process

  1. Read context: Look at relevant source files, existing patterns, and related commands to understand the current state.
  2. Ask questions about:
    • What the user wants to achieve (feature, bug fix, refactor, etc.)
    • Which commands, providers, or utilities are affected
    • Expected behavior and edge cases
    • Whether i18n is needed (new user-visible strings)
    • Whether new dependencies or config changes are required
    • Whether the VS Code extension (vscode-sfdx-hardis) is affected: load the vscode-sfdx-hardis skill and grep the extension for the commands, flags, config keys and WebSocket events involved
  3. Iterate: Keep asking until you are confident you understand the full scope.
  4. Summarize your understanding:
    • Goal: What we're trying to achieve
    • Scope: Files and areas affected
    • Requirements: Specific requirements and constraints
    • i18n impact: Whether translations are needed
    • VS Code extension impact: What changes in vscode-sfdx-hardis, or "none" with the reason
    • Open questions: Any remaining uncertainties

Do NOT proceed to design or implementation. Your only job is to understand the problem.

$ARGUMENTS

© hardisgroupcom, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/analyze of hardisgroupcom/sfdx-hardis.

Open the folder on GitHubat commit 971ac89

Compare with similar skills

Analyze next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyze this skillhardisgroupcom/sfdx-hardis400—~484Automated safety check: PassAGPL-3.0
GSD Phase Discussionopen-gsd/gsd-core10k1 repos~1.5kAutomated safety check: WarnMIT
Web Console Local Tracesforcedotcom/salesforcedx-vscode1k—~796Automated safety check: PassBSD-3-Clause
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
Claude Docs Consultantcentminmod/my-claude-code-setup2.7k—~959Automated safety check: PassMIT
Services Extension Consumptionforcedotcom/salesforcedx-vscode1k—~5kAutomated safety check: PassBSD-3-Clause

Similar skills

  • GSD Phase Discussion

    open-gsd/gsd-core

    Asks adaptive questions about a project phase and records the decisions in a CONTEXT.md that later research and planning agents can act on without asking again.

    10k GitHub starsUsed in 1 repo~1.5k tokens
    Agent WorkflowsAuto-check: warnings
  • Web Console Local Traces

    forcedotcom/salesforcedx-vscode

    Unblock hosted Web Console OTLP to localhost:4318. An agent skill from forcedotcom/salesforcedx-vscode.

    1k GitHub stars~796 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Claude Docs Consultant

    centminmod/my-claude-code-setup

    Consult official Claude Code documentation from code.claude.com using selective fetching.

    2.7k GitHub stars~959 tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed
  • Services Extension Consumption

    forcedotcom/salesforcedx-vscode

    Consume the salesforcedx-vscode-services extension API. An agent skill from forcedotcom/salesforcedx-vscode.

    1k GitHub stars~5k tokensUpdated today
    Sales & SupportAuto-check passed
  • Changelog Entry

    certinia/debug-log-analyzer

    Write, review or trim CHANGELOG.md entries. An agent skill from certinia/debug-log-analyzer.

    114 GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from hardisgroupcom/sfdx-hardis

All 21 skills in this repo
  • Promotion Branches E2E Test

    hardisgroupcom/sfdx-hardis

    Runs a full end-to-end test of sfdx-hardis promotion branches and backpromote against real Salesforce orgs and a throwaway repository, then writes a report.

    400 GitHub stars~4.7k tokensUpdated today
    Auto-check: notes
  • sfdx-hardis Training End-to-End Test

    hardisgroupcom/sfdx-hardis

    Walks the sfdx-hardis training course end to end as a learner would, against a real Developer Edition org and fork, fixing broken steps and screenshots that no longer match.

    400 GitHub stars~2.6k tokensUpdated today
    Auto-check: notes
  • sfdx-hardis Architecture Guide

    hardisgroupcom/sfdx-hardis

    Explains how the sfdx-hardis Salesforce CLI plugin is built: its TypeScript and Oclif stack, command layout, agent-mode flag and provider classes for git, notifications and AI.

    400 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Changelog Style Rules

    hardisgroupcom/sfdx-hardis

    Style rules for adding CHANGELOG.md entries: short, user-facing bullets grouped by command under the beta section, each linking the command's docs page.

    400 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Documentation

    hardisgroupcom/sfdx-hardis

    Documentation standards for sfdx-hardis commands (description format with Command Behavior and Technical explanations sections, MkDocs site, build:doc).

    400 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Fix Jscpd

    hardisgroupcom/sfdx-hardis

    Decision framework for fixing jscpd (copy-paste detector) errors.

    400 GitHub stars~613 tokensUpdated today
    Auto-check passed

Questions about Analyze

What does Analyze do?

Gather requirements by asking clarifying questions until the problem is fully understood. Analyze is an agent skill from hardisgroupcom/sfdx-hardis. Gather requirements by asking clarifying questions until the problem is fully understood.

When should I use Analyze?

Analyze fits situations like: tasks that involve Requirements gathering.

How do I install Analyze in Claude Code?

Run `npx skills add hardisgroupcom/sfdx-hardis --skill analyze -a claude-code`. Or copy the skill folder (.claude/skills/analyze in hardisgroupcom/sfdx-hardis) into .claude/skills/analyze in your project. Claude Code loads it when a task matches its description.

How do I install Analyze in Codex?

Run `npx skills add hardisgroupcom/sfdx-hardis --skill analyze -a codex`. Or copy the skill folder (.claude/skills/analyze in hardisgroupcom/sfdx-hardis) into .agents/skills/analyze in your project. Codex loads it when a task matches its description.

Can I use Analyze in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hardisgroupcom/sfdx-hardis --skill analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze, .gemini/skills/analyze, .github/skills/analyze and .opencode/skills/analyze in your project.

What does Analyze need to run?

SKILL.md names no scripts, command-line tools or credentials: Analyze is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebSearch, WebFetch, AskUserQuestion.

Does Analyze access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Analyze safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Analyze use?

Analyze is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analyze use?

About 484 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Analyze?

Skills that share tags, products or a category with Analyze: GSD Phase Discussion (open-gsd/gsd-core, 10k stars), Web Console Local Traces (forcedotcom/salesforcedx-vscode, 1k stars), Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars) and Claude Docs Consultant (centminmod/my-claude-code-setup, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyze?

hardisgroupcom (a GitHub organization) maintains it in hardisgroupcom/sfdx-hardis, which has 400 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.

Source: hardisgroupcom/sfdx-hardis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.