Spectra analyze

Skill chenwei791129/es-log-cli/.claude/skills/spectra-analyze

Read-only, agent-friendly Elasticsearch log query CLI

Install

npx -y skills add chenwei791129/es-log-cli --skill spectra-analyze

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze artifact consistency for a change

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.4 KB, 702 tokens by cl100k_base, as published. Nobody here has run it

Claude fork context

This generated Claude Code skill runs with context: fork. The rules in this section take precedence over the shared analyze body below.

When no change name is provided, run spectra list --json. Auto-select only when there is exactly one active change. If there are zero active changes or more than one active change, return the candidate list or empty-state message and ask the main thread to rerun /spectra-analyze <change-name>. Do NOT ask an interactive selection question inside the fork.

Analyze artifact consistency for a change. Can be invoked directly or triggered automatically when all artifacts are complete.

Input: Optionally specify a change name (e.g., /spectra-analyze add-auth). If omitted, infer from conversation context or auto-select if only one active change exists.

Prerequisites: This skill requires the spectra CLI. If any spectra command fails with "command not found" or similar, report the error and STOP.

Steps

Determine change name

If not provided, infer from context or run spectra list --json to auto-select.
Run programmatic analysis
```
spectra analyze <change-name> --json
```
This returns structured JSON with:
- dimensions: Array of { dimension, status, finding_count } for Coverage, Consistency, Ambiguity, Gaps
- findings: Array of { id, dimension, severity, location, summary, recommendation }
- artifacts_analyzed / artifacts_missing: Which artifacts were available

Present results

Format the JSON output as a readable summary:

## Artifact Analysis: <change-name>

| Dimension     | Status                   |
|---------------|--------------------------|
| Coverage      | <status>                 |
| Consistency   | <status>                 |
| Ambiguity     | <status>                 |
| Gaps          | <status>                 |

Group findings by severity (Critical > Warning > Suggestion) with locations and recommendations.

Supplement with AI semantic analysis (optional)

The programmatic analyzer catches structural issues. For deeper semantic analysis, also read the artifacts and check for:
- Design decisions that contradict spec requirements
- Tasks referencing work outside proposal scope
- Risks in design without corresponding spec coverage
- Logical inconsistencies between artifacts
Add any additional findings to the report.
Recommend next steps
- If CRITICAL findings: "Found N issue(s) worth addressing. Want to fix these before implementing?"
- If only warnings/suggestions: Note them briefly, then recommend proceeding with /spectra-apply
- If clean: "Artifacts look consistent" and suggest /spectra-apply

Passive Trigger

When spectra status --change "<name>" --json shows isComplete: true, run this analysis automatically before recommending /spectra-apply.

Guardrails

Read-only: NEVER modify files
Do NOT prompt for change selection if it can be inferred
Keep output concise - this runs inline, not as a separate workflow
If AskUserQuestion tool is not available, ask the same questions as plain text and wait for the user's response

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most research analysis skills give in 702 tokens

Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07

Generate a markdown reportin 32 of 1063, across 23 files
Cite each claim's sourcein 30 of 1063, across 15 files
Define the ideal customer profilein 20 of 1063, across 2 files
Search for companies matching the criteriain 20 of 1063, across 2 files
Assign a fit score from one to tenin 20 of 1063, across 2 files
Analyze the codebase to understand the productin 19 of 1063, across 1 file
Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
Look for signals of immediate needin 19 of 1063, across 1 file
Identify the target decision maker rolein 19 of 1063, across 1 file
Suggest a personalized contact strategyin 19 of 1063, across 1 file
Provide conversation starters for outreachin 19 of 1063, across 1 file
Format results in a scannable markdown templatein 19 of 1063, across 1 file

Said here and by no other author read

run spectra list to find active changes
auto-select only when exactly one active change exists
ask main thread to rerun when multiple changes exist
stop and report if spectra command is missing
run spectra analyze with the change name
check artifacts for semantic inconsistencies

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.