Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-seo-agentic
saas-seo-agentic
UnverifiedAudit & implement IsItAgentReady Level 0-5 standards (RFC 9727, llms.txt, MCP cards, JWKS).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.0 KB |
| references/access-policy.md | markdown | 6.1 KB |
| references/agent-auth-and-identity.md | markdown | 3.6 KB |
| references/agent-friendly-pages.md | markdown | 5.1 KB |
| references/agentic-commerce-protocols.md | markdown | 2.2 KB |
| references/discovery-and-markdown.md | markdown | 6.7 KB |
| references/dns-aid-and-link-headers.md | markdown | 1.9 KB |
| references/isitagentready-levels.md | markdown | 4.2 KB |
| references/lighthouse-agentic-category.md | markdown | 6.3 KB |
| references/vendor-matrix.md | markdown | 5.0 KB |
| references/webmcp.md | markdown | 6.1 KB |
references/dns-aid-and-link-headers.md
View on GitHub# DNS-AID & RFC 8288 Link Headers
Network-layer and HTTP-header discovery mechanisms that allow agents to locate APIs, catalogs, and endpoints before crawling HTML.
---
## 1. DNS for AI Discovery (DNS-AID)
Publish discovery records under your domain's `_agents` DNS namespace using `SVCB` or `HTTPS` records with `alpn` and `port` connection parameters:
```dns
_a2a._agents.example.com. 3600 IN SVCB 1 agent.example.com. alpn="a2a" port=443 mandatory=alpn,port
_index._agents.example.com. 3600 IN HTTPS 1 . alpn="h2,h3"
_catalog._agents.example.com. 3600 IN TXT "url=https://example.com/.well-known/ai-catalog.json"
_search._agents.example.com. 3600 IN SRV 10 1 443 search.example.com.
```
### Requirements
- Use numeric `keyNNNNN` SvcParamKey names for experimental custom DNS-AID parameters until IANA registration.
- Enable **DNSSEC** on the zone so validating DNS-over-HTTPS resolvers (`cloudflare-dns.com/dns-query`, `dns.google/resolve`) return `AD: true` (Authenticated Data).
---
## 2. RFC 8288 / RFC 9727 §3 `Link` Response Headers
Return `Link` headers on the homepage HTTP response pointing to machine-readable resources (multiple `Link` headers or comma-separated values are both valid):
```http
Link: </.well-known/api-catalog>; rel="api-catalog"
Link: </openapi.json>; rel="service-desc"; type="application/openapi+json"
Link: </docs>; rel="service-doc"; type="text/html"
Link: </llms.txt>; rel="describedby"; type="text/plain"
Link: </.well-known/ai-catalog.json>; rel="ai-catalog"; type="application/ai-catalog+json"
```
### Registered Relation Types Checked by Agent Scanners
- `api-catalog` -> RFC 9727 linkset catalog
- `service-desc` -> OpenAPI / machine service description
- `service-doc` -> Human/developer documentation
- `describedby` -> Machine-readable site description (e.g., `/llms.txt` or schema)
- `ai-catalog` -> ARD capability manifest
- `alternate` (`type="text/markdown"`) -> Markdown representation of the page
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |