connect-dataforseo
Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub
Walks the user through connecting their DataForSEO account so Omnipresence can pull SERP, keyword, backlink, on-page, and LLM-mention data without an Ahrefs or Semrush subscription. Trigger when the user says any of "connect dataforseo", "set up dataforseo", "connect my dataforseo", "set up SEO data", "connect a SEO data source", "wire up dataforseo", "add my dataforseo credentials", "set up AIO measurement". This is the ONE canonical DataForSEO credential-setup flow. Walks them through: DataForSEO signup (if needed), retrieving their API login + API password (separate from the dashboard login password) from https://app.dataforseo.com/api-dashboard, saving credentials locally to ~/.claude/.omni-dataforseo.json (never to the synapse fork, never to our servers), and validating with one cheap test call to the user_data endpoint. ~3 minutes total. Idempotent — safe to re-run to rotate the password or update the login.
In this repository23 other files it gives its agents.
- connect-emailSkill
- connect-google-cloudSkill
- connect-openaiSkill
- continue-strategySkill
- create-workerSkill
- disconnect-dataforseoSkill
- disconnect-emailSkill
- disconnect-google-cloudSkill
- disconnect-openaiSkill
- domain-migration-checklistSkill
- fill-project-gapSkill
- getting-startedSkill
- list-projectsSkill
- list-strategiesSkill
- load-workerSkill
- new-projectSkill
- new-strategySkill
- project-infoSkill
- project-resolverSkill
- push-changesSkill
- reload-workerSkill
- switch-projectSkill
- sync-omnipresenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 10 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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
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.

