Get Started Agent Skill

Set up an SEO task by choosing an outcome and checking available evidence. Use for onboarding the SEO plugin.

593 tokens

context cost

SKILL.md, read when the skill is used

files

plus reference files

copies elsewhere

how many repositories repackaged it

834

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/AgriciDaniel/chatgpt-seo --skill get-started

178 bytes besides the instruction

agents/openai.yaml

6 sections, as written by the author

The user's desired SEO outcome and any URL, draft or export already supplied.

If a skill-resource reader fails to open a linked supporting file, try the

available file or execution tool using the installed plugin root returned by

the host or resolved from this skill's location. Do not hardcode a home folder,

version, or working directory. Distinguish a failed reader call from an absent

file, and files actually attempted from files not attempted. Report a resource

as unavailable only after the supported access paths have failed. If no file

or execution access is available, continue within the evidence you can read

and state that limit.

Read the operating contract when this

workflow is selected. Use runtime and data paths

when choosing a tool or handling missing data. Recheck relevant

search facts and primary sources

before date-sensitive claims. For a quantitative diagnostic, read

scoring; unavailable categories stay unknown.

Explain in one sentence that the plugin turns supplied or accessible evidence into a practical SEO plan.
If a concrete task and input are already present, start the matching workflow immediately. Do not force an onboarding questionnaire.
Otherwise ask one question: what site, page, draft or dataset should we work on? Offer site audit, page improvement, content brief or export diagnosis as examples.
Check available browsing, file and execution tools, then describe only the capabilities relevant to this task.
For an unavailable account source, offer the applicable export path. Do not request API keys, install runtimes or alter connections.
Start with evidence and state the scope. Publisher details can be given if requested; onboarding does not solicit contact information.

A concrete first task or a single useful intake question, followed by immediate progress when the input is available.

No account, payment, email address or publisher contact is needed for the supplied-file workflows.

Copy the folder

Take agricidaniel/get-started from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.