01046b01e4
Umfangreiche Erweiterung der Skill-Bibliothek: Neue Skills für Humanisierung (Englisch/PT-BR), Design-Validierung, AI-SEO und Coolify-Deployment inkl. Regelwerke, Presets, Pattern-Referenzen, Testfälle und Automatisierungsskripte. Zusätzliche Skills für Revenue-Centric Design, Pier Cloud, OKF, Lebenslauf- und LinkedIn-Optimierung sowie zahlreiche Referenzdateien, Checklisten und YAML/JSON/Markdown-Templates. Einführung einer vollständigen OpenWiki-Dokumentation mit Architektur-, Domain- und Workflow-Beschreibungen, zentralem Index und automatisierten Updates. Modularer Aufbau, restriktive Lizenzen und umfassende Qualitäts- und Evaluationsmechanismen für alle neuen Inhalte.
44 lines
2.4 KiB
Markdown
44 lines
2.4 KiB
Markdown
---
|
|
name: agent-ready-auth-md
|
|
description: >
|
|
Sub-skill de agent-ready-cloudflare: Skill: Implement Auth.md Agent Registration Discovery
|
|
---
|
|
# Skill: Implement Auth.md Agent Registration Discovery
|
|
|
|
## What This Skill Does
|
|
|
|
Helps a service publish Auth.md support for agent registration. Use this when a scanner reports the `authMd` check is failing or when adding the Auth.md standard to an API or application.
|
|
|
|
## Requirements
|
|
|
|
- Serve `/auth.md` from the service root as Markdown with an H1 heading that contains `auth.md` (for example, `# auth.md` or `# Example auth.md`).
|
|
- Prefer publishing OAuth Protected Resource Metadata at `/.well-known/oauth-protected-resource` for the resource server.
|
|
- Include `resource`, `authorization_servers`, `scopes_supported`, and `bearer_methods_supported` with `header` in the PRM document.
|
|
- Publish OAuth Authorization Server metadata at each advertised authorization server's `/.well-known/oauth-authorization-server` URL.
|
|
- Include a valid `issuer` in Authorization Server metadata and ensure it matches the issuer advertised in PRM.
|
|
- Add an `agent_auth` block with `skill`, `register_uri`, and at least one complete registration method when Authorization Server metadata is available.
|
|
- If OAuth metadata is not available, keep `/auth.md` self-contained: identify the agent audience, document registration or provisioning endpoint(s), list supported method(s), and explain credential use.
|
|
|
|
## Flow Metadata
|
|
|
|
- **ID-JAG**: include `identity_types_supported: ["identity_assertion"]`, `identity_assertion.assertion_types_supported` with `urn:ietf:params:oauth:token-type:id-jag`, and credential types. Include `revocation_uri` and the revocation event in `events_supported` when supported.
|
|
- **Verified email**: include `identity_assertion.assertion_types_supported` with `verified_email`, credential types, and `claim_uri`.
|
|
- **Anonymous**: include `identity_types_supported: ["anonymous"]`, `anonymous.credential_types_supported`, and `claim_uri`.
|
|
|
|
## Validate
|
|
|
|
```http
|
|
POST https://isitagentready.com/api/scan
|
|
Content-Type: application/json
|
|
|
|
{"url": "https://YOUR-SITE.com"}
|
|
```
|
|
|
|
Check that `checks.discovery.authMd.status` is `"pass"`.
|
|
|
|
## References
|
|
|
|
- [Auth.md Specification](https://auth-md.com)
|
|
- [RFC 9728 — OAuth Protected Resource Metadata](https://www.rfc-editor.org/rfc/rfc9728)
|
|
- [RFC 8414 — OAuth Authorization Server Metadata](https://www.rfc-editor.org/rfc/rfc8414)
|