agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/Employee-Self-Service-Agent-Developer-Kit/solutions/ess-maker-skills/src/skills/analytics/SKILL.md

analytics

Skill29 starsChanged 6 months agoMITView on GitHub

Print a direct link to the current DA agent's Copilot Studio analytics dashboard, so the maker can jump straight from VS Code to its usage metrics. Every Message block is the exact text to show the user. Copy it verbatim. Do not rephrase, add commentary, or tell the user what tools you are calling or files you are reading. The behavior is intentionally a thin wrapper over the scripts/analytics_pointer.py CLI: this skill file only decides which message block to show;…

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every Message block is the exact text to show the user.

    line 6
  2. Very specific:

    Run python scripts/analytics_pointer.py --status in the terminal and capture its stdout as JSON.

    line 24
  3. Distinctive:

    Do not add any additional Message block after the script output in this case.

    line 85
  4. Very specific:

    If the maker explicitly asks to "stop showing the analytics reminder" or similar, run python scripts/analytics_pointer.py --dismiss in the …

    line 109
  5. Very specific:

    Stop here. Do NOT run --dismiss unless the maker explicitly asked.

    line 121

“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Analytics Skill

Print a direct link to the current DA agent's Copilot Studio analytics dashboard, so the maker can jump straight from VS Code to its usage metrics.

Every Message block is the exact text to show the user. Copy it verbatim. Do not rephrase, add commentary, or tell the user what tools you are calling or files you are reading.

The behavior is intentionally a thin wrapper over the scripts/analytics_pointer.py CLI: this skill file only decides which message block to show; the pointer resolution and URL construction happen inside the script. The skill records one adk.capability.use event for the analytics capability when it starts.

Start

First run python scripts/analytics_pointer.py --record-invocation to emit one capability-usage event for this /analytics invocation. This is best-effort and must not block the skill.

Run python scripts/analytics_pointer.py --status in the terminal and capture its stdout as JSON. The JSON has the shape:

{
  "flag": "on" | "off",
  "association": null | { "env_id": "...", "agent_id": "..." },
  "url": "https://...",
  "reason": "" | "feature_flag_off" | "missing_association" | "validation_failed",
  "completed": true | false
}

Then branch on that JSON exactly as follows. Do not compose your own message. If a branch has no Message block, stay silent and stop.

Case 1: explicit opt-out (flag == "off")

The analytics link was explicitly disabled with ADK_ANALYTICS_POINTER=off. Do not substitute the Copilot Studio homepage.

Message:

Your Copilot Studio analytics link isn't available in this workspace right now. Please contact your administrator for help accessing analytics.

End message.

Stop here.

Case 2: flag ON, association missing (flag == "on" AND association == null)

This is the FR7 repair state. Either .local/config.json doesn't have an active DA agent linked, or one of env_id / agent_id is missing. The fix is /setup.

Message:

I can't find a linked DA Copilot Studio agent for this workspace, so I can't build an analytics link yet. Run /setup to link an agent, then run /analytics again.

End message.

Stop here.

Case 3: flag ON, association present, URL resolved (url is non-empty)

Show the link exactly as returned by the script — do NOT shorten it, wrap it in a tracker, or reformat the URL. Then run python scripts/analytics_pointer.py --show in the terminal. That command prints the same maker-facing line the pointer would print. Show the script's stdout verbatim to the maker — that is the ONLY output the maker sees.

Do not add any additional Message block after the script output in this case. The script's output IS the message.

Case 4: flag ON, association present, resolution failed (url empty AND reason is validation_failed)

Reserved for the click-time destination-validation stub (FR2). Today the resolver never returns this; when the FR2 check lands, this branch will fire on transient failures.

Message:

I couldn't validate the Copilot Studio analytics link right now. Try running /analytics again in a moment.

End message.

Stop here.

Optional: dismissing the reminder

If the maker explicitly asks to "stop showing the analytics reminder" or similar, run python scripts/analytics_pointer.py --dismiss in the terminal. That marks the one-time post-deployment reminder complete for the current local DA workspace association. Then:

Message:

Got it — I won't show the post-deployment analytics reminder again. You can still run /analytics any time to jump to the dashboard.

End message.

Stop here. Do NOT run --dismiss unless the maker explicitly asked.

Download now (ZIP)

  • Other versions67 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 67

    1. coreyhaines31/marketingskills★ 58ksame name
    2. getsentry/sentry★ 46ksame name
    3. thewh1teagle/vibe★ 7.7ksame name
    4. microsoft/power-platform-skills★ 1.1ksame name
    5. Nexus-JPF/note-companion★ 870same name
    6. microsoft/rayfin★ 646same name
    7. LedgerHQ/ledger-live★ 622same name
    8. Cesarjoquin/Marketing-Skills★ 190same name
    9. microsoft/awesome-rayfin★ 108same name
    10. TheAceTeam/CC-Flight★ 93same name

    57 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use popups, free-tools and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • CesarjoquinSkill

      popups

      When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

      Also in 22 projects that use this

    • CesarjoquinSkill

      free-tools

      When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

      Also in 23 projects that use this

    • coreyhaines31Skill

      marketing-council

      When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

      Also in 18 projects that use this

    • pixelswithblissSkill

      co-marketing

      When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referral-program. For launch-specific partnerships, see launch-strategy.

      Also in 22 projects that use this

    • ukunal91appSkill

      community-marketing

      Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel.

      Also in 25 projects that use this

    • roerohanSkill

      emails

      When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

      Also in 18 projects that use this

    • +6 more from Cesarjoquin
  • In this repository42 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free