agentleFS
omnipresence-osomnipresence-os/claude-skills/connect-openai/SKILL.md

connect-openai

Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub

Walks the user through connecting their OpenAI API key so any Omnipresence skill that supports the `provider:openai` toggle (today — dataforseo-ai-visibility's Method A/B OpenAI-direct path; future — additional AI-search collectors) can call OpenAI directly instead of going through DataForSEO's wrapper. Trigger when the user says any of "connect openai", "set up openai", "connect my openai", "add my openai key", "wire up openai", "save my openai api key", "configure openai for omnipresence", "use openai for GEO research", "switch GEO to openai". This is the ONE canonical OpenAI credential-setup flow. Walks them through retrieving an API key at https://platform.openai.com/api-keys, saving credentials locally to ~/.claude/.omni-openai.json (never to the synapse fork, never to our servers), and validating the key with one zero-cost GET to /v1/models. ~2 minutes total. Idempotent — safe to re-run to rotate keys or update the account.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

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