Aiconfig Agent Graphs
Resolve legacy `aiconfig-agent-graphs` references and send the agent to the current `agent-graphs` skill.
Overview
aiconfig-agent-graphs is a journey-wide agent skill that redirects legacy invocations to the renamed `agent-graphs` skill—usable whenever an old reference surfaces before graph work starts.
Install
npx skills add https://github.com/launchdarkly/agent-skills --skill aiconfig-agent-graphsWhat is this skill?
- Hard stop: do not run graph tasks here—invoke `agent-graphs` only
- Backward compatibility for `aiconfig-agent-graphs` in old docs and prompts
- Apache-2.0 stub at version 0.1.0
- Explicit rename map: `aiconfig-agent-graphs` → `agent-graphs`
- Renamed to `agent-graphs`
- metadata version 0.1.0
Adoption & trust: 1k installs on skills.sh; 16 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your workflow still calls `aiconfig-agent-graphs`, but instructions and behavior now live only under `agent-graphs`.
Who is it for?
Unblocking agents stuck on a renamed graph skill identifier after a repo or catalog update.
Skip if: Defining or editing agent graphs—use `agent-graphs` end to end.
When should I use this skill?
Legacy automation or prompts invoke `aiconfig-agent-graphs` instead of `agent-graphs`.
What do I get? / Deliverables
The session pivots to `agent-graphs` for real graph authoring, and you update persistent configs to the new slug.
- Handoff to invoke `agent-graphs`
- Updated configs using `agent-graphs` slug
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
A multi-agent pipeline references `aiconfig-agent-graphs` from an old blog post copy-paste.
You compare graph-oriented skills in Prism and land on the stub while hunting the real `agent-graphs` entry.
Pre-ship you grep the repo for deprecated skill IDs and patch manifests to `agent-graphs`.
How it compares
Compatibility alias only; not a graph DSL or runtime integration.
Common Questions / FAQ
Who is aiconfig-agent-graphs for?
Solo builders and agent runners who maintain skill manifests and hit the obsolete `aiconfig-agent-graphs` name from older LaunchDarkly agent-skills docs.
When should I use aiconfig-agent-graphs?
When automation explicitly loads `aiconfig-agent-graphs`—in build agent-tooling you redirect to `agent-graphs`; in idea research when tracing which skill powers a demo graph; in ship review when verifying skill slugs in release notes.
Is aiconfig-agent-graphs safe to install?
It is inert task-wise, but confirm trust via the Security Audits panel on this page and standardize on `agent-graphs` in new installs.
Workflow Chain
Then invoke: agent graphs
SKILL.md
READMESKILL.md - Aiconfig Agent Graphs
# Deprecated — renamed to `agent-graphs` This skill has been renamed. **Do not follow any instructions here and do not perform the task from this skill.** Invoke the **`agent-graphs`** 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-agent-graphs` to `agent-graphs`.