agentleFS
replynodesreplynodes/replynodes-agent-skills/skills/brand-intelligence/SKILL.md

brand-intelligence

Skill3 starsChanged 3 months agoMITView on GitHub

Internal: brand identity research guidance, merged into brand-kit. Route public brand identity retrieval for a known domain to brand-kit; this slug is not a separate public successor.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Never paste, expose, commit, or log the key.

    line 31

≈ “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

ReplyNodes brand intelligence (internal)

This is an internal compatibility skill. Agent-skills issue #57 (canonical taxonomy #56) merged brand-intelligence guidance into the canonical brand-kit skill. The public successor for brand identity retrieval is brand-kit; install that slug.

What to do instead

  • Public brand identity for one known domain → brand-kit: GET https://brand.replynodes.com/{domain} (free, zero-auth, read-only).
  • Logo-only intent → brand-logo.
  • Keyed brand operations (/v1/brand/search, /v1/brand/retrieve, /v1/brand/fonts, /v1/brand/styleguide, /v1/brand/logo) via https://mcp.replynodes.com/mcp or the REST origin https://api.replynodes.com with REPLYNODES_API_KEY in a secret store.

Never paste, expose, commit, or log the key. Run initialize and tools/list on MCP; the live schema is authoritative. This skill remains read-only: it retrieves public signals only and cannot modify brand assets, accounts, or websites.

Migration

brand-intelligence is not a public successor and is not deleted in issue #57; it is retained as internal migration guidance pointing to brand-kit. Registry side unpublish/redirect and readback are owned by issue #58.

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.