Instrumentieren Sie ein LaunchDarkly-Metrikereignis in einer Codebasis, indem Sie einen track()-Aufruf hinzufügen. Verwenden Sie dies, wenn der Benutzer ein Ereignis einrichten, eine Aktion für eine Metrik instrumentieren, ein Tracking zu einer Funktion hinzufügen oder bestätigen möchte, dass ein Ereignis in LaunchDarkly fließt.
Diese Fähigkeit ermöglicht es einem KI-Agenten, eine LaunchDarkly-Metrik in einer Codebasis zu instrumentieren, indem ein `track()`-Aufruf eingefügt wird. Sie ist besonders nützlich für Entwickler, die Ereignisse für Experimente, Feature-Tracking oder Analysen mit LaunchDarkly einrichten möchten. Die Fähigkeit analysiert den vorhandenen Code, um die geeignete LaunchDarkly-Client-Instanz und den Metriknamen zu identifizieren, und fügt dann den `track()`-Aufruf an der richtigen Stelle ein. Sie unterstützt verschiedene Programmiersprachen und Frameworks, darunter JavaScript/TypeScript, Python, Java, Go und Ruby, und kann sowohl im Backend als auch im Frontend eingesetzt werden. Der Agent überprüft, ob die Aktion erfolgreich ausgeführt wurde, und bietet bei Bedarf Optionen zum Rückgängigmachen. Diese Automatisierung spart Zeit und reduziert menschliche Fehler bei der Einrichtung von Metriken, was besonders in Continuous-Integration- und Deployment-Pipelines wertvoll ist.
npx skills add https://github.com/launchdarkly/agent-skills/tree/main/skills/launchdarkly-metric-instrumentInstalled? Explore more Produktivität & Zusammenarbeit skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
Instrumentieren Sie ein LaunchDarkly-Metrikereignis in einer Codebasis, indem Sie einen track()-Aufruf hinzufügen. Verwenden Sie dies, wenn der Benutzer ein Ereignis einrichten, eine Aktion für eine Metrik instrumentieren, ein Tracking zu einer Funktion hinzufügen oder bestätigen möchte, dass ein Ereignis in LaunchDarkly fließt.
This repo contains 20 individual skills — each has its own dedicated page.
DEPRECATED redirect — this skill was renamed to agent-graphs. Do not use this skill; invoke agent-graphs instead. Kept only so old references to aiconfig-agent-graphs still point users to the new name.
DEPRECATED redirect — this skill was renamed to built-in-metrics. Do not use this skill; invoke built-in-metrics instead. Kept only so old references to aiconfig-ai-metrics still point users to the new name.
DEPRECATED redirect — this skill was renamed to configs-create. Do not use this skill; invoke configs-create instead. Kept only so old references to aiconfig-create still point users to the new name.
DEPRECATED redirect — this skill was renamed to custom-metrics. Do not use this skill; invoke custom-metrics instead. Kept only so old references to aiconfig-custom-metrics still point users to the new name.
DEPRECATED redirect — this skill was renamed to migrate. Do not use this skill; invoke migrate instead. Kept only so old references to aiconfig-migrate still point users to the new name.
DEPRECATED redirect — this skill was renamed to online-evals. Do not use this skill; invoke online-evals instead. Kept only so old references to aiconfig-online-evals still point users to the new name.
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.
DEPRECATED redirect — this skill was renamed to snippets. Do not use this skill; invoke snippets instead. Kept only so old references to aiconfig-snippets still point users to the new name.
DEPRECATED redirect — this skill was renamed to configs-targeting. Do not use this skill; invoke configs-targeting instead. Kept only so old references to aiconfig-targeting still point users to the new name.
DEPRECATED redirect — this skill was renamed to tools. Do not use this skill; invoke tools instead. Kept only so old references to aiconfig-tools still point users to the new name.
DEPRECATED redirect — this skill was renamed to configs-update. Do not use this skill; invoke configs-update instead. Kept only so old references to aiconfig-update still point users to the new name.
DEPRECATED redirect — this skill was renamed to configs-variations. Do not use this skill; invoke configs-variations instead. Kept only so old references to aiconfig-variations still point users to the new name.
Apply LaunchDarkly SDK onboarding: install dependency (or dual-SDK pair), configure env and secrets with consent, add init at entrypoint(s), verify compile. Nested under sdk-install; next is run.
Detect repository stack for LaunchDarkly SDK onboarding: languages, frameworks, package managers, monorepo targets, entrypoints, existing LD usage. Nested under sdk-install; next is plan.
Create a boolean first flag, add evaluation, toggle on/off for end-to-end proof. Parent onboarding Step 6; uses MCP, API, or ldcli; optional flag-create skill.
Set up and run experiments in LaunchDarkly. Create experiments with metrics, treatments, and flag config, start iterations to collect data, swap design between iterations, and stop with a winner.
Safely remove a feature flag from code while preserving production behavior. Use when the user wants to remove a flag from code, delete flag references, or create a PR that hardcodes the winning variation after a rollout is complete.
Create and configure LaunchDarkly feature flags in a way that fits the existing codebase. Use when the user wants to create a new flag, wrap code in a flag, add a feature toggle, or set up an experiment. Guides exploration of existing patterns before creating.
Audit your LaunchDarkly feature flags to understand the landscape, find stale or launched flags, and assess removal readiness. Use when the user asks about flag debt, stale flags, cleanup candidates, flag health, or wants to understand their flag inventory.
Control LaunchDarkly feature flag targeting including toggling flags on/off, percentage rollouts, targeting rules, individual targets, and copying flag configurations between environments. Use when the user wants to change who sees a flag, roll out to a percentage, add targeting rules, or promote config between environments.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.