
Aiconfig Targeting
Resolve stale prompts or automations that still name aiconfig-targeting and route you to the renamed LaunchDarkly configs-targeting skill.
Overview
Aiconfig Targeting is an agent skill for the Build phase that only redirects deprecated references to the configs-targeting skill—do not run targeting from this package.
Install
npx skills add https://github.com/launchdarkly/agent-skills --skill aiconfig-targetingWhat is this skill?
- Explicit DEPRECATED status in skill frontmatter
- Hard stop: do not follow instructions in this skill body
- Redirects all work to configs-targeting with complete current instructions
- Apache-2.0 metadata version 0.1.0 preserved for traceability
- Documents rename from aiconfig-targeting for docs and saved prompts
- Renamed to configs-targeting; version 0.1.0 in metadata
Adoption & trust: 1.3k installs on skills.sh; 16 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent or docs still call aiconfig-targeting and you risk following obsolete or empty instructions.
Who is it for?
Builders hitting legacy skill IDs in LaunchDarkly agent-skills who need a explicit rename pointer in the agent.
Skip if: Anyone implementing flag or AI config targeting—use configs-targeting exclusively.
When should I use this skill?
An old reference, documentation link, or automation still names aiconfig-targeting and you need the correct skill slug.
What do I get? / Deliverables
You immediately switch to configs-targeting and update old references from aiconfig-targeting to configs-targeting.
- Updated references from aiconfig-targeting to configs-targeting
- Invocation of configs-targeting for actual targeting tasks
Recommended Skills
Journey fit
Deprecated integration aliases belong on the Build integrations shelf because they exist only to preserve wiring to feature-flag config targeting. Integrations subphase reflects redirect-only skills that point to the current LaunchDarkly agent skill rather than executing targeting logic here.
How it compares
Meta redirect stub, not the active LaunchDarkly targeting skill package.
Common Questions / FAQ
Who is aiconfig-targeting for?
Developers or agents with outdated skill names in prompts, CI, or internal docs that still reference aiconfig-targeting.
When should I use aiconfig-targeting?
Only when an old automation invoked this slug by mistake—instantly replace the call with configs-targeting during Build integrations work.
Is aiconfig-targeting safe to install?
It is low-risk as a redirect, but confirm via the Security Audits panel on this page; perform real config changes only through configs-targeting.
Workflow Chain
Then invoke: configs targeting
SKILL.md
READMESKILL.md - Aiconfig Targeting
# Deprecated — renamed to `configs-targeting` This skill has been renamed. **Do not follow any instructions here and do not perform the task from this skill.** Invoke the **`configs-targeting`** 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-targeting` to `configs-targeting`.