aiconfig-projects

DEPRECATED redirect — this skill was renamed to projects. Do not use this skill; invoke projects instead. Kept only so old references to aiconfig-projects still point users to the new name.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/agentcontrol/aiconfig-projects/SKILL.md

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an exemplary deprecation stub: lean, unambiguous, and actionable, with clear organization and no nested references. It does exactly what a redirect skill should with no wasted tokens.

Dimension	Reasoning	Score
Conciseness	The body is a lean four-line stub with no concept explanation or padding; every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.	3 / 3
Actionability	It gives concrete, specific guidance—name the replacement skill exactly ('projects') and update references from 'aiconfig-projects' to 'projects'—which is copy-paste-ready for a redirect stub.	3 / 3
Workflow Clarity	This is a simple single-action skill (do not use; invoke projects; update stale references) and the action is unambiguous, so per the simple-skills scoring note workflow clarity can score 3.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external file references, it is well-organized with a clear heading and points to a sibling skill rather than nested files, satisfying the simple-skill progressive-disclosure criterion.	3 / 3
	Total	12 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is clear and honest about being a deprecated redirect with a specific, low-conflict trigger, but as a skill description it lacks an explicit 'Use when...' trigger clause and offers only narrow keyword coverage, capping completeness and trigger quality at the mid level.

Suggestions

Add an explicit 'Use when an old reference names aiconfig-projects' trigger clause to lift completeness above 2.

Include a couple more natural trigger variants (e.g. 'aiconfig project', 'AI config projects') to broaden trigger-term coverage.

Lead with the redirect action and keep the rationale second so the capability statement reads as concrete actions first.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('invoke projects instead', 'update it from aiconfig-projects to projects') but they are redirect/meta actions rather than a comprehensive list of skill capabilities, so it sits at the 'names domain and some actions' anchor rather than the multi-capability anchor above.	2 / 3
Completeness	The 'what' is explicit (deprecated redirect; invoke projects), and the 'when' is only implied via 'Kept only so old references... still point users' with no 'Use when...' clause, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	It surfaces the key natural terms a user with an old reference would say ('aiconfig-projects', 'projects'), but coverage is narrow and missing common variations, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	It targets the very specific old name 'aiconfig-projects' and only fires for stale references to that name, giving it a clear niche unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: launchdarkly/ai-tooling
Path: skills/agentcontrol/aiconfig-projects/SKILL.md
Commit: e6ab09b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.