verify-challenge

Verify OWASP Juice Shop challenge entries against metadata, configuration, localization, and test requirements.

Updated May 13, 2026
One-click install
npx skills add https://github.com/tolonlo/FinalCiber --skill verify-challenge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-challenge
Source: https://github.com/tolonlo/FinalCiber/tree/main/.ai/skills/verify-challenge
Command: npx skills add https://github.com/tolonlo/FinalCiber --skill verify-challenge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents newly added challenges from breaking discovery, configuration, translations, or automated testing in OWASP Juice Shop.

Core Features & Use Cases

  • Challenge YAML quality control: Ensures data/static/challenges.yml entries meet naming, key, category, difficulty, hints, tags, mitigations, and disabledEnv conventions.
  • Configuration integration checks: Confirms the challenge key is correctly wired into both config.schema.yml and config/fbctf.yml.
  • Localization coverage: Verifies frontend/src/assets/i18n/en.json contains required category/tag translation keys when new labels are introduced.
  • Optional content validation: Checks the presence and expected structure of hacking instructor scripts and coding challenge files when applicable.
  • Test safety alignment: Verifies tests are guarded when disabledEnv is used to avoid environment-incompatible failures.

Quick Start

Use the verify-challenge skill to review a new challenge entry by checking data/static/challenges.yml, CTF mappings in config.schema.yml and config/fbctf.yml, required translation keys, and the corresponding tutorial/code/test artifacts.

Frequently Asked Questions about verify-challenge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a new OWASP Juice Shop challenge meets metadata and configuration requirements?

To verify new OWASP Juice Shop challenges, validate entries in `data/static/challenges.yml` for schema compliance, check `config.schema.yml` and `config/fbctf.yml` CTF mappings, and confirm `disabledEnv` conventions are met to prevent configuration breaks.

What does challenge localization coverage validation involve in OWASP Juice Shop?

Localization coverage validation confirms `frontend/src/assets/i18n/en.json` contains required category and tag translation keys when new labels are introduced, ensuring newly added challenges render correctly across supported languages.

Why do my automated tests fail when adding a Juice Shop coding challenge with `disabledEnv`?

Tests fail when `disabledEnv` flags are not properly aligned with environment-guarded test suites. You must verify tests are guarded to avoid environment-incompatible failures during challenge onboarding workflows.

Do I need to include hacking instructor scripts when validating a new Juice Shop challenge?

You must check for the presence and expected structure of optional hacking instructor scripts and coding challenge files when applicable, ensuring all optional content artifacts are validated during challenge onboarding.

How do I ensure OWASP mitigation references are valid for a new Juice Shop challenge?

To ensure valid OWASP mitigation references, verify that newly added `data/static/challenges.yml` entries meet naming, key, category, difficulty, hints, tags, and mitigation conventions specified by the repository schema.

What is the best way to check CTF country mappings for a new OWASP Juice Shop challenge?

The best way to check CTF country mappings is to confirm the challenge `key` is correctly wired into both `config.schema.yml` and `config/fbctf.yml`, ensuring proper discovery and configuration integration.