Lint scenario data for missing fields, taxonomy violations, and credentials.
npx skills add https://github.com/whatsper/texterdocs --skill validate-scenarios
Please help me install this Agent Skill. Skill: validate-scenarios Source: https://github.com/whatsper/texterdocs/tree/main/.claude/skills/validate-scenarios Command: npx skills add https://github.com/whatsper/texterdocs --skill validate-scenarios
Lint src/data/scenarios.ts for missing fields, taxonomy violations, undocumented trigger/action types, and unsanitized credentials, then run npm run build.
The skill reads the live definitions from the source-of-truth (src/data/scenarios.ts) and cross-checks every scenario against the taxonomy in .claude/skills/add-scenario/SKILL.md. It validates required fields, tag taxonomy, trigger consistency, action types, and credential sanitization to ensure safe, publish-ready data. It surfaces actionable findings as errors or warnings and guides remediation.
Ask the skill to validate scenarios to lint the marketplace data and verify the build is healthy.
High-intent search queries and answers about installing and using this skill.
To lint scenarios for missing fields and taxonomy violations, validate the scenarios array against the required fields and tag taxonomy defined in your source-of-truth files. The process cross-checks data to surface actionable errors and warnings.
Checking for unsanitized credentials in data files involves applying defined rules to scan for sensitive data within your scenarios. The validation surfaces credential leaks as findings without auto-fixing them, ensuring publish-ready data.
When trigger and action types are undocumented in scenarios, the validation process flags these inconsistencies by cross-checking them against the documentation mapping. It reports these discrepancies as errors or warnings to guide remediation.
You cannot fully validate scenario data without running a build process, because the validation concludes by executing npm run build. This step verifies that the marketplace data is healthy and the application compiles successfully.
Scenario validation does not automatically fix credential leaks. It surfaces sensitive data findings using defined rules and guides remediation, requiring explicit user requests before applying any auto-fixes to the data.
whatsperAppend sanitized JSON scenarios to Texter's src/data/scenarios.ts with TypeScript-safe validation.
IgniteUICompile and bundle the Ignite UI for Angular library with npm build commands.
vanhoangkhaValidate compliance framework JSON syntax, check existence, and verify requirement ID uniqueness in pull requests.
rnavarychImplement data validation with Zod, Joi, class-validator, Pydantic, and JSON Schema.
