aiconfig-create▌
launchdarkly/agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You're using a skill that will guide you through setting up AI configuration in your application. Your job is to explore the codebase to understand the use case and stack, choose agent vs completion mode, create the config following the right path, and verify it works.
Create AI Config
You're using a skill that will guide you through setting up AI configuration in your application. Your job is to explore the codebase to understand the use case and stack, choose agent vs completion mode, create the config following the right path, and verify it works.
Prerequisites
- LaunchDarkly API access token with
ai-configs:writepermission or MCP server - LaunchDarkly project (use
aiconfig-projectsskill if needed)
Core Principles
- Understand the Use Case First: Know what you're building before choosing a mode
- Choose the Right Mode: Agent mode vs completion mode depends on your framework and needs
- Two-Step Creation: Create config first, then create variations (model, prompts, parameters)
- Verify via API: The agent fetches the config to confirm it was created correctly
API Key Detection
- Check environment variables —
LAUNCHDARKLY_API_KEY,LAUNCHDARKLY_API_TOKEN,LD_API_KEY - Check MCP config — Claude:
~/.claude/config.json→mcpServers.launchdarkly.env.LAUNCHDARKLY_API_KEY - Prompt user — Only if detection fails
Workflow
Step 1: Understand Your Use Case
Before creating, identify what you're building:
- What framework? LangGraph, LangChain, CrewAI, OpenAI SDK, Anthropic SDK, custom
- What does the AI need? Just text, or tools/function calling?
- Agent or completion? See decision below
Step 2: Choose Agent vs Completion Mode
| Your Need | Mode |
|---|---|
| Persistent instructions across interactions | Agent |
| LangGraph, CrewAI, AutoGen | Agent |
| Direct OpenAI/Anthropic API calls | Completion |
| Full control of message structure | Completion |
| One-off text generation | Completion |
Both modes support tools. Agent mode: single instructions string. Completion mode: full messages array.
Step 3: Create the Config
Follow API Quick Start for curl examples:
- Create config —
POST /projects/{projectKey}/ai-configs(key, name, mode) - Create variation —
POST /projects/{projectKey}/ai-configs/{configKey}/variations(instructions or messages, modelConfigKey, model.parameters) - Attach tools — After creation, PATCH variation to add tools (see
aiconfig-toolsskill)
Step 4: Verify
After creation, verify the config:
-
Fetch via API:
curl -X GET "https://app.launchdarkly.com/api/v2/projects/{projectKey}/ai-configs/{configKey}" \ -H "Authorization: {api_token}" -H "LD-API-Version: beta" -
Confirm:
- Config exists with correct mode
- Variations have model names (not "NO MODEL")
- modelConfigKey is set
- Parameters are present
-
Report results:
- ✓ Config created with correct structure
- ✓ Variations have models assigned
- ⚠️ Flag any missing model or parameters
- Provide config URL:
https://app.launchdarkly.com/projects/{projectKey}/ai-configs/{configKey}
Important Notes
- modelConfigKey must be
{Provider}.{model-id}(e.g.,OpenAI.gpt-4o) for models to show in UI - Tools must be created first (
aiconfig-toolsskill), then attached via PATCH - Tools endpoint is
/ai-tools, NOT/ai-configs/tools
Edge Cases
| Situation | Action |
|---|---|
| Config already exists | Ask if user wants to update instead |
| Variation shows "NO MODEL" | PATCH variation with modelConfigKey and model |
| Invalid modelConfigKey | Use values from model-configs API |
What NOT to Do
- Don't create configs without understanding the use case
- Don't skip the two-step process (config then variation)
- Don't try to attach tools during initial creation
- Don't forget modelConfigKey (models won't show)
Related Skills
aiconfig-tools— Create tools before attachingaiconfig-variations— Add more variations for experimentationaiconfig-update— Modify configs based on learnings
References
How to use aiconfig-create on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add aiconfig-create
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches aiconfig-create from GitHub repository launchdarkly/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate aiconfig-create. Access the skill through slash commands (e.g., /aiconfig-create) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★26 reviews- ★★★★★Dhruvi Jain· Dec 8, 2024
aiconfig-create fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Oshnikdeep· Nov 27, 2024
Registry listing for aiconfig-create matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Oct 18, 2024
aiconfig-create reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Michael Agarwal· Sep 25, 2024
aiconfig-create fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Anika Zhang· Sep 17, 2024
We added aiconfig-create from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sakshi Patil· Sep 9, 2024
I recommend aiconfig-create for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Rahul Santra· Sep 5, 2024
aiconfig-create has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chaitanya Patil· Aug 28, 2024
Useful defaults in aiconfig-create — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Pratham Ware· Aug 24, 2024
Solid pick for teams standardizing on skills: aiconfig-create is focused, and the summary matches what you get after install.
- ★★★★★Michael Khanna· Aug 16, 2024
We added aiconfig-create from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 26