agentleFS
ai-search-guruai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/skills/report/SKILL.md

report

Skill432 starsChanged 12 days agoMITView on GitHub

Citations, mentions and share of voice: what changed and why. Ready to share with your team.

98 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use export, resume and 6 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.
  • soilmassSkill

    export

    Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.

    Also in 4 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 7 projects that use this

  • tokyubevoxelverseSkill

    checkup

    Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.

    Also in 3 projects that use this

  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 5 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 3 projects that use this

  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read 7 days of answers on all tracked platforms.

    line 31
  2. Distinctive:

    Write the report in the layout below.

    line 33
  3. Distinctive:

    Never claim a change caused another: say what moved together, and when.

    line 50
  4. Distinctive:

    Keep it internal and truthful: report drops as plainly as gains.

    line 51

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

Weekly report

A one-page report a team can read in two minutes: where the brand stands in AI answers this week, what changed, and what to do next.

When to use

  • "Write this week's report", "Give me a weekly recap", "What should I tell the team on Monday?"
  • For another period, follow the same layout with the period the person names.

What to read

  1. Seven days of answers: get_overview_summary, or get_visibility_summary for this week and for last week, on every tracked platform.
  2. get_visibility_trend by day for the two weeks.
  3. get_mentions_summary: mention rate and sentiment against the week before.
  4. get_competitor_comparison for this week and last: share of voice against competitors.
  5. list_citations for both weeks: the pages that gained or lost citations.
  6. get_prompt_performance sorted by visibility, both ways, for the biggest gainers and losers.
  7. list_action_center_tasks sorted by priority, open ones only, and get_action_history for actions closed this week.

Steps

  1. Read 7 days of answers on all tracked platforms.
  2. Compare with last week: citations, mentions and share of voice.
  3. Write the report in the layout below.

Output

Weekly report · {first day} to {last day}

  1. Summary: three bullets, the most important first.
  2. Numbers: a table with Metric, This week, Last week and Change, for citations, mentions, share of voice and visibility.
  3. What changed and why: the prompts, pages and platforms that moved most, up and down, with their numbers and what moved with them.
  4. Competitors: who gained or lost share of voice.
  5. Next week: the three Action Center actions to work on, by priority, and what closed this week.

End with the date of the newest data the report used.

Don't

  • Chat doesn't email the report: the person keeps it with Save to Files or downloads it, and sends it to the team.
  • Never claim a change caused another: say what moved together, and when. An outcome before day 30 is a reading so far.
  • Keep it internal and truthful: report drops as plainly as gains.

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.