Aiconfig Tools
Resolve stale prompts that still call aiconfig-tools by redirecting the agent to the renamed tools skill without executing deprecated instructions.
Overview
aiconfig-tools is an agent skill for the Build phase that only redirects legacy references to the renamed tools skill and must not be executed for configuration work.
Install
npx skills add https://github.com/launchdarkly/agent-skills --skill aiconfig-toolsWhat is this skill?
- Hard stop: do not follow instructions in this skill body
- Explicit redirect to the tools skill for current behavior
- Preserves old automation and doc references to aiconfig-tools
- Apache-2.0 licensed metadata stub at version 0.1.0
- Zero operational steps—rename-only migration pointer
Adoption & trust: 1.5k installs on skills.sh; 16 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your prompts or pipelines still call aiconfig-tools after LaunchDarkly renamed the skill, so agents might follow stale or empty instructions.
Who is it for?
Migrating old skill slugs in saved agent configs without hunting broken links.
Skip if: Anyone trying to configure LaunchDarkly AI tools—use the tools skill directly and remove this alias from new setups.
When should I use this skill?
Only when an old reference still names aiconfig-tools; then redirect to tools and do not execute this skill.
What do I get? / Deliverables
The agent stops, skips deprecated steps, and invokes tools so AI config tasks run against current instructions; you update references from aiconfig-tools to tools.
- Redirect decision to invoke tools
- Updated prompts replacing aiconfig-tools with tools
Recommended Skills
Journey fit
Build agent-tooling is where LaunchDarkly AI-config skills live; this entry exists only as a compatibility alias on that shelf. Agent-tooling subphase reflects renamed agent capability packaging rather than a standalone integration task.
How it compares
Meta redirect stub, not a substitute for the full tools integration skill.
Common Questions / FAQ
Who is aiconfig-tools for?
Builders cleaning up legacy agent skill names who still have aiconfig-tools in old documentation or automation.
When should I use aiconfig-tools?
Only when an agent is routed here by mistake; immediately switch to tools for any real Build-phase agent-tooling or AI config work.
Is aiconfig-tools safe to install?
Check the Security Audits panel on this Prism page; the skill intentionally performs no task other than pointing to tools.
Workflow Chain
Then invoke: tools
SKILL.md
READMESKILL.md - Aiconfig Tools
# Deprecated — renamed to `tools` This skill has been renamed. **Do not follow any instructions here and do not perform the task from this skill.** Invoke the **`tools`** skill instead — it contains the current, complete instructions. If you arrived here from an old reference (documentation, a saved prompt, or automation), update it from `aiconfig-tools` to `tools`.