brand-profile
Skill3 starsChanged 3 months agoMITView on GitHub
Internal: brand profile guidance, merged into brand-kit. For a known domain, use brand-kit's free, read-only brand host; this slug is not a separate public successor.
- Reads credentials
In this repository18 other files it gives its agents.
- llms.txtllms.txt
- replynodesSkill
- app-store-apiSkill
- brand-fontsSkill
- brand-intelligenceSkill
- brand-kitSkill
- brand-logoSkill
- brand-searchSkill
- brand-styleguideSkill
- company-researchSkill
- competitor-researchSkill
- google-play-apiSkill
- pdf-to-markdownSkill
- reddit-apiSkill
- url-to-markdownSkill
- web-scrapingSkill
- web-searchSkill
- youtube-apiSkill
The file
Files
ReplyNodes brand profile (internal)
This is an internal compatibility skill. Agent-skills issue #57 (canonical
taxonomy #56) merged brand-profile guidance into the canonical
brand-kit skill. The public successor is
brand-kit.
What to do instead
For a single known domain, request the free, zero-auth brand host — no API key, account, signup, MCP server, or credits are required:
curl --fail-with-body https://brand.replynodes.com/replynodes.comSend a bare public domain only — no scheme, port, path, query, or credentials.
www. and a trailing slash are normalized. GET https://brand.replynodes.com/
returns a small usage document. Append .json for the machine-readable
readback. The canonical contract is the
Brand intelligence guide,
and the full response shape and field list live in
brand-kit.
Anonymous limits and errors (reconciled to production)
The brand host shares the anonymous quota with the Markdown host: 20 admitted
requests per trusted client-IP bucket per UTC day, with X-RateLimit-Limit,
X-RateLimit-Remaining, and X-RateLimit-Reset on every anonymous response.
Over the limit the response is HTTP 429 anonymous_limit_reached with a
Retry-After header and a continuation object pointing at
https://docs.replynodes.com/docs/auth (an existing authenticated free account
has 500 credits). Standard outcomes are 400 invalid_request,
405 method_not_allowed, 502 upstream_unavailable, 503 degraded
(fail-closed), and 504 gateway_timeout. Earlier guidance describing a
per-minute IP limit and a 429 rate_limited envelope was superseded by the
shared anonymous daily quota shipped in fetcher #715/#727.
Optional authenticated continuation
The same upstream capability backs the keyed /v1/brand/* routes. Use
https://mcp.replynodes.com/mcp with Authorization: Bearer ${REPLYNODES_API_KEY}
in a secret store, or the REST origin https://api.replynodes.com with the same
bearer key, for authentication, billing, bulk, or programmatic access. Never
paste, expose, or log the key; run initialize and tools/list on MCP.
Migration
brand-profile 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.
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.