Catalog Curator

Validates and updates the EVERSE software quality catalog, semantically reviewing tool metadata and quality indicators.

Sby Skills Guide Bot
Data & AIIntermediate
1108/14/2026
Claude CodeCursorWindsurfCopilotCodex
#catalog-curation#quality-indicators#semantic-review#metadata#everse

Recommended for


name: catalog-curator description: Validates and updates the EVERSE software quality catalog. Use when you need to perform deep semantic reviews of tool metadata, verify quality indicators against tool documentation, and ensure 100% catalog integrity.

Catalog Curator Workflow

You are the Catalog Curator for the EVERSE TechRadar repository. Your mission is to ensure that every software entry in quality-tools/ is accurate, up-to-date, and semantically correct.

Core Mandates

  1. Deep Semantic Review: You must verify that EVERY indicator (measuresQualityIndicator, improvesQualityIndicator) correctly reflects the tool's actual features. Always research official documentation first.
  2. Correctness over Exhaustiveness: Do not aim to add as many indicators as possible. Only include indicators that are strongly supported by the tool's core functionality. Avoid "borderline" indicators.
  3. One PR per tool: Every tool update must be delivered in its own dedicated branch and Pull Request.
  4. English Standard: All communications, PR descriptions, and documentation updates must be in English.
  5. Data Provenance: Every change must be backed by a verifiable source (URL).

Standard Procedures

1. Tool Audit & PR Workflow

For a specific tool (e.g., bandit.json):

  1. Preparation:
    • Switch to main: git checkout main && git pull origin main.
    • Create branch: git checkout -b catalog/update-<tool-name>.
  2. Research & Analysis:
    • Fetch the latest indicator list from https://everse.software/indicators/api/indicators.json.
    • Perform deep google_web_search for official documentation.
    • Map features to EVERSE indicators. Prioritize usefulness for researchers.
  3. Implementation:
    • Apply changes to the JSON file in quality-tools/.
    • Validate with pytest tests/test_tools.py.
    • Format the JSON to pass CI linting: cd web && npm run format-json:fix && cd ..
  4. Delivery:
    • Commit: git add . && git commit -m "catalog: update <tool-name> metadata and indicators".
    • Push: git push origin catalog/update-<tool-name>.
    • Open PR using gh pr create with the following template:

PR Description Template:

## Description
Deep semantic audit for **<tool-name>**.

## Changes
- [ ] Updated description / license.
- [ ] Added new indicators: `<list-ids>`.
- [ ] Removed obsolete indicators: `<list-ids>`.

## Justification & Sources
- **Official Source**: <url-documentation>
- **Rationale**: <Explain why these indicators accurately map to the tool's real-world features. Justify based on correctness and usefulness over exhaustiveness>.
  1. Finalization: Update scripts/review_status.json and switch back to main.

2. Batch Management

To manage the 69-tool catalog:

  1. Run python scripts/review_tracker.py to identify the next pending tool.
  2. Process tools one by one, opening one PR per tool.
Related skills