agentleFS
Sign inStart free
CyrusNuevoDiaCyrusNuevoDia/skill-language-server/.agents/skills/analytics/SKILL.md

analytics

Skill7 starsChanged 4 months agoMITView on GitHub

Collect and explain public download and usage signals for Skill Language Server across npm, Open VSX, Zed, and future distribution channels. Use when asked for $analytics, an analytics pulse, extension adoption, package downloads, install trends, channel comparisons, or charts and tables about product usage.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects 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 23 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 24 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 19 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 21 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 26 projects that use this

  • coreyhaines31Skill

    marketing-loops

    When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'weekly ads check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'run my SEO,' 'SEO operator,' 'daily SEO agent,' 'run my outbound,' 'AI SDR,' 'reply triage,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

    Also in 10 projects that use this

  • +6 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use --days N to change the trailing window (default: 30).

    line 18
  2. Distinctive:

    Read the collector's JSON and lead with a compact Markdown table.

    line 24
  3. Distinctive:

    Keep the npm and Open VSX charts separate because their download events have different meanings.

    line 25
  4. Distinctive:

    Add two to four concise takeaways grounded in the returned values.

    line 26
  5. Distinctive:

    Keep the caveat that downloads are events or proxies, not people.

    line 29
  6. Distinctive:

    Do not sum npm, Open VSX, and Zed counts into “total users.” Zed installs can trigger npm downloads, retries and CI can inflate npm, and …

    line 31
  7. Distinctive:

    Read references/sources.md when a source breaks or when adding a channel.

    line 33
  8. Distinctive:

    Use the source-provided lifetime count when available.

    line 39
  9. Distinctive:

    Never infer active users, retention, or editor market share from these public counters.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 58 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

Produce a current, source-backed distribution pulse without presenting downloads as unique users.

Run the collector

From the repository root, run:

node .agents/skills/analytics/scripts/fetch-analytics.mjs

Use --days N to change the trailing window (default: 30). Run --help for the complete interface. The collector always emits JSON; interpret that data yourself instead of asking the script to generate prose or presentation.

The collector queries all sources concurrently and reports a failed source explicitly while preserving successful results. Treat a partial result as partial; never claim every channel was checked when one failed.

Present the pulse

  1. Read the collector's JSON and lead with a compact Markdown table.
  2. Keep the npm and Open VSX charts separate because their download events have different meanings.
  3. Add two to four concise takeaways grounded in the returned values.
  4. State the data-through date for lagging daily sources.
  5. Link each source page in the final answer.
  6. Keep the caveat that downloads are events or proxies, not people.

Do not sum npm, Open VSX, and Zed counts into “total users.” Zed installs can trigger npm downloads, retries and CI can inflate npm, and marketplace downloads are not identity-deduplicated.

Read references/sources.md when a source breaks or when adding a channel. Read references/reporting.md before changing metric definitions or presentation rules.

Verify before reporting

  • Confirm generatedAt is from the current run.
  • Confirm every requested channel is either ok or visibly listed as unavailable.
  • Use the source-provided lifetime count when available; do not reconstruct it from a short trend window.
  • Describe the current UTC day as partial when a source includes it. npm intentionally ends at the last complete UTC day.
  • Never infer active users, retention, or editor market share from these public counters.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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