Highcharts Tooling Guardrails
SkillDev toolsKeeps your agent's code changes aligned with Highcharts' existing build and test tooling instead of adding new ones.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Highcharts Tooling Guardrails skill
About this capability
Keep changes aligned with the existing Highcharts tooling stack and avoid introducing ad-hoc or inconsistent build/test infrastructure.
What this skill tells your AI
The instructions your AI receives, as published by highcharts/highcharts in .agents/skills/tooling/SKILL.md and read by ahel’s review.
Use this skill for changes in tools/, build scripts, test runners, or repository automation.
Rules
- Reuse existing tooling first:
- Prefer npm scripts, gulp tasks, eslint/playwright setup, and existing helpers under
tools/. - Do not add a new toolchain when equivalent behavior already exists.
- Keep stack consistency:
- Prefer Node-based scripts for cross-platform support unless shell behavior is explicitly required.
- Avoid adding repo-wide dependencies for one-off automation.
- Keep automation safe and predictable:
- Default scripts to non-destructive behavior.
- Require explicit confirmation flags for destructive replacements.
- Support non-interactive CI mode.
- Verify tooling changes:
- Add or update usage docs/help output (
--help) for new scripts. - Include a minimal validation checklist in task/PR output with exact commands used.
Output format
For each tooling change:
- Change
- Why this stack choice
- Validation command(s)
Signals
- GitHub stars
- 12k
- Forks
- 4k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
tooling-highcharts- Source
- github.com/highcharts/highcharts