verify-challenge

Verify new Juice Shop challenges for metadata, CTF config, and documentation.

13.6k|19.0k|Updated Sep 19, 2014
One-click install
npx skills add https://github.com/juice-shop/juice-shop --skill verify-challenge-juice-shop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-challenge
Source: https://github.com/juice-shop/juice-shop/tree/main/.ai/skills/verify-challenge
Command: npx skills add https://github.com/juice-shop/juice-shop --skill verify-challenge-juice-shop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or inconsistent Juice Shop challenge additions by providing a structured verification workflow before merging changes.

Core Features & Use Cases

  • Challenge metadata validation: Checks uniqueness, formatting, category/tag validity, hint quality, and optional mitigation URL correctness for entries in challenges.yml.
  • CTF integration checks: Verifies the challenge key is wired into config.schema.yml and config/fbctf.yml without mapping conflicts.
  • Operational readiness auditing: Ensures translations exist for new categories/tags and that tests respect disabledEnv constraints.
  • Support-file coverage: Confirms required hacking-instructor scripts and coding challenge assets exist when those features are enabled.

Quick Start

Use this Skill to review a newly proposed challenge key end-to-end across challenges.yml, CTF config, translations, optional scripts, optional codefixes, and associated tests for correctness.

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 is correctly configured before merging?

To verify a new OWASP Juice Shop challenge, validate metadata in challenges.yml, check CTF integration in config.schema.yml and fbctf.yml, ensure translation coverage, and confirm test guards respect disabledEnv constraints before merging.

What does CTF integration validation for Juice Shop challenges include?

CTF integration validation checks that the challenge key is wired into config.schema.yml and config/fbctf.yml without mapping conflicts, ensuring the new challenge is properly registered for CTF competitions.

How do I check if hacking-instructor scripts and coding challenge assets exist for a new challenge?

Support-file coverage auditing confirms required hacking-instructor scripts and codefix assets exist and follow project conventions when those optional companion features are enabled for the new challenge.

Why are my Juice Shop challenge tests failing when environment variables disable certain features?

Tests for new challenges must respect disabledEnv constraints to prevent failures in restricted environments. Verification ensures disabledEnv-aware tests are properly guarded so challenge verification passes across all configurations.

Do I need to add translations for new challenge categories and tags in Juice Shop?

Yes, operational readiness auditing verifies that translation i18n entries exist for any new categories and tags introduced in challenges.yml, ensuring the challenge is fully documented across all supported languages.