Skip to content

Conversation

@sergical
Copy link
Member

@sergical sergical commented Jan 31, 2026

Summary

  • Implements the Cloudflare Agent Skills Discovery RFC to expose documentation skills at /.well-known/skills/
  • Allows AI coding assistants to discover and use Sentry documentation when helping users implement SDKs

Skills exposed:

Skill Purpose
sentry-docs SDK setup, configuration, and troubleshooting
technical-docs Documentation writing guidelines
docs-review Sentry style guide for reviewers

Documentation pages added:

  • /agentic-usage/ - For SDK users using AI agents
  • /contributing/agentic-usage/ - For doc contributors

Note: Skill files are copied at build time instead of using symlinks because Vercel doesn't follow symlinks.

Test plan

  • yarn build succeeds
  • yarn build:developer-docs succeeds
  • Preview: verify /.well-known/skills/index.json returns skills manifest
  • Preview: verify /.well-known/skills/sentry-docs/SKILL.md returns content
  • Preview: verify /agentic-usage/ page renders
  • Preview: verify /contributing/agentic-usage/ page renders

🤖 Generated with Claude Code

Implements the Cloudflare Agent Skills Discovery RFC to expose
documentation skills at /.well-known/skills/. This allows AI coding
assistants to discover and use Sentry documentation when helping
users implement SDKs.

Skills exposed:
- sentry-docs: SDK setup, configuration, and troubleshooting
- technical-docs: Documentation writing guidelines
- docs-review: Sentry style guide for reviewers

Also adds documentation pages:
- /agentic-usage/ for SDK users
- /contributing/agentic-usage/ for doc contributors

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Jan 31, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview, Comment Jan 31, 2026 10:04pm
sentry-docs Ready Ready Preview, Comment Jan 31, 2026 10:04pm

Request Review

Vercel doesn't follow symlinks during build. This adds a copy-skills
script that copies skill files from .claude/skills/ to
public/.well-known/skills/ during build.

Co-Authored-By: Claude <noreply@anthropic.com>
Comment on lines +9 to +19
"name": "technical-docs",
"description": "Write and review technical documentation for Sentry SDK docs. Use when creating, editing, or reviewing documentation pages, especially MDX files in docs/platforms/.",
"files": ["SKILL.md"]
},
{
"name": "docs-review",
"description": "Review documentation for Sentry style and voice. Use when reviewing or writing user-facing documentation to ensure it follows the Sentry documentation style guide.",
"files": ["SKILL.md"]
}
]
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The global trailingSlash: true setting will cause a redirect for /.well-known/skills/index.json, which may break clients expecting a direct file response.
Severity: HIGH

Suggested Fix

Add a specific configuration rule in vercel.json or next.config.ts to create an exception for the /.well-known/skills/index.json path, disabling the trailing slash redirect for this specific file to ensure it is served directly.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: public/.well-known/skills/index.json#L1-L19

Potential issue: The global `trailingSlash: true` configuration in both `next.config.ts`
and `vercel.json` will cause requests for the `/.well-known/skills/index.json` file to
receive a 308 redirect to `/.well-known/skills/index.json/`. This behavior contradicts
the standard convention for serving JSON files and will likely cause issues for clients
attempting to discover skills, as they typically expect a direct file response without a
trailing slash and may not handle the redirect correctly.

Did we get this right? 👍 / 👎 to inform future reviews.

Copy link
Member Author

@sergical sergical Jan 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants