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

start

Skill432 starsChanged 11 days agoMITView on GitHub

Answers setup questions and walks through the open Getting started steps, with a link to each page.

135 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-audio 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.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +5 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 122 edited versions we read keep these.

  • 5

    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 only these, for the chat's brand:

    line 17
  2. Distinctive:

    When the workspace has two brands or more and none is selected, ask which brand to set up first.

    line 27
  3. Distinctive:

    When every step is done, say so and point to the brand's first results instead.

    line 35
  4. Distinctive:

    Never mark a Getting started step done or skip one: it completes through its own check.

    line 47
  5. Distinctive:

    Add competitors, topics or prompts only with the tools that do it, and the app asks the person first.

    line 48

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

Get started

The playbook of the /start shortcut ("Help me get started. What should I set up first?"): what to set up next in GetCito, from where the brand stands today.

Data plan

Read only these, for the chat's brand:

  1. get_onboarding_progress: the Getting started steps, done and open, in stage order.
  2. list_competitors, list_topics and list_prompts: how many competitors, topics and prompts the brand has.
  3. list_connections: whether Google Search Console and Analytics are connected for the brand.
  4. get_plan_facts, only when an open step depends on what the plan includes.
  5. list_brands only when no brand is selected, and open_page to link each step's page.

Questions

  • When the workspace has two brands or more and none is selected, ask which brand to set up first.
  • Nothing else: the progress answers the rest.

Steps

  1. Say where the brand stands in one line: how many steps are done, out of how many.
  2. List the open steps in stage order, five at most. For each: what it needs, why it matters for AI answers, and its page, linked with open_page.
  3. For anything the person connects themselves (Search Console, Analytics, the AI Traffic snippet), give the short steps they take.
  4. When every step is done, say so and point to the brand's first results instead.

Output

Text: the one-line status, then the open steps as a numbered list.

Next moves

The next open steps, such as "Add 3 competitors" or "Connect Google Search Console".

Don't

  • Never mark a Getting started step done or skip one: it completes through its own check.
  • Add competitors, topics or prompts only with the tools that do it, and the app asks the person first.

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.