agentleFS
Sign inStart free
advisorppc-orgadvisorppc-org/advisorseo-claude-plugin/skills/connect-and-import/SKILL.md

connect-and-import

Skill0 starsChanged 28 days agoMITView on GitHub

Use for setting up a website in AdvisorSEO, for example "add my site", "connect my website", "set up AdvisorSEO", "import my site", "connect WordPress", "connect Google Search Console", "what platform is my site on", or "fill in my business profile". Detects the site's platform, creates the site record, saves the business profile, and explains where WordPress and Google connections are made.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    Never ask for a password, API key, token or authorization header in the chat.

    line 15
  2. Very specific:

    Check gravity_list_sites before creating a site, so the same domain is not added twice.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Connect and import a site

Why: every other skill works from the site record and the business profile. Getting them right once saves a wrong answer in every later conversation.

Rules that come first

  1. Never ask for a password, API key, token or authorization header in the chat. Google is connected through a consent link the site owner opens in their own browser.
  2. Creating a site, updating it and saving the profile are writes. Show the preview, wait for the user's yes in a new turn, then call with confirm=true.
  3. Check gravity_list_sites before creating a site, so the same domain is not added twice.
  4. Any rate you report comes with its n plus an interval, or the words "insufficient data". Never state an AI rank position.

Steps

  1. gravity_overview() then gravity_list_sites(): is the domain already there?
  2. gravity_detect_platform for the domain: WordPress, Shopify or another platform. This decides how pages are published later.
  3. gravity_create_site with name and domain. Preview, approval turn, then confirm. Keep the site_id it returns.
  4. gravity_get_profile(site_id), then gravity_set_profile(site_id, ...) with business name, type, location, brand voice, target audience, selling points, services and hours. Ask the user for what you do not know. Preview, approval turn, then confirm.
  5. WordPress: the user creates an application password in WordPress (Users, Profile, Application Passwords) and stores it with the site address on the site record, either in the web app or with gravity_update_site (preview, approval turn, confirm). The first publish preview in approve-and-measure-change tests the connection.
  6. Google Search Console, Analytics and Tag Manager: gravity_google_connect_url(site_id) gives a link that expires in 10 minutes. The site owner opens it, signs in with the Google account that can see the property, and allows the read-only Search Console and Analytics permissions. Tag Manager asks for its own link on first use. Then gravity_gsc_sites and gravity_google_set_properties choose the property. See search-console, analytics-ga4 and tag-manager-tracking.
  7. Optional: gravity_crawl_site to import the site's pages so audits and plans start from what exists. gravity_crawl_pages reads the imported pages.
  8. Finish with ai-readiness-check as the first useful result.

Check

The lead's eval proves this skill when the reply calls gravity_list_sites before gravity_create_site, calls gravity_detect_platform, never asks for a password or key in chat, points Google connection to app.advisorseo.ai, and passes confirm=true only after a user approval turn.

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