feat: add Factory settings MCP skill

[sarahlessner]

Summary

• Playbook for configuring Factory (auto-flagging / auto-releasing + GitHub repo → project mapping) via the hosted LaunchDarkly MCP.
• Depends on the tools in gram-functions#276, which call the alpha /api/v2/account/factory-settings REST directly — those endpoints are gated by enable-factory-settings and are deliberately not on the public API spec.
• Skill states the alpha gate explicitly: if every Factory tool 404s, the account isn't in the alpha, and the agent should say so rather than retry or fall back to REST.
• Agents use owner/name and list-factory-github-repos; they must not send autoCleanup or install the GitHub App.

Testing

• Manual: python3 scripts/validate_skills.py, python3 scripts/generate_catalog.py --check, python3 -m unittest discover -s tests
• Skill tool names verified against the tools once they're attached to catfood Gram

Notes

• Land after #276 is deployed and attached, otherwise the skill references tools no client can see.
• gonfalon#72408 replaces the closed #72402: it keeps the operation-description improvements (master-gate semantics, numeric repo id, projectKey on create, omit autoCleanup) without publishing Factory to the public OpenAPI spec.

Made with Cursor

Link to Devin session: https://app.devin.ai/sessions/c1daee83b7234d9fb3df996cb78e3f86
Open in Devin Desktop: https://app.devin.ai/desktop/session/c1daee83b7234d9fb3df996cb78e3f86?variant=devin
Requested by: @sarahlessner

[github-actions]

Skill eval results

Skill	Before	After	Δ
agentcontrol/configs-create	100/100 (4/4)	100/100 (4/4)	no change
agentcontrol/configs-update	80/100 (4/5)	80/100 (4/5)	no change
agentcontrol/configs-variations	80/100 (4/5)	80/100 (4/5)	no change
agentcontrol/tools	75/100 (3/4)	75/100 (3/4)	no change
feature-flags/flag-and-release-change	-	100/100 (4/4)	new
feature-flags/flag-release	-	100/100 (5/5)	new
feature-flags/launchdarkly-flag-command	-	100/100 (3/3)	new
feature-flags/launchdarkly-flag-create	100/100 (3/3)	100/100 (4/4)	no change
feature-flags/launchdarkly-flag-drift	-	100/100 (4/4)	new
feature-flags/should-flag-change	-	100/100 (17/17)	new
onboarding	-	75/100 (3/4)	new

Only suites whose source actually changed since their last recorded score were re-run. Soft-failing while we stabilise the baseline.

[sarahlessner]

@sattensil I tagged you in this one since you're doing so much great work on skills for factory I thought you might have some input on this skill around updating our factory settings. This is part of a larger effort to make it so you can do all the settings that are available in the UI through the MCP