Skip to content

[ELI5] Adding ELI5 skill into GitHub#28651

Open
Oxyjun wants to merge 1 commit intoproductionfrom
jun/eli5
Open

[ELI5] Adding ELI5 skill into GitHub#28651
Oxyjun wants to merge 1 commit intoproductionfrom
jun/eli5

Conversation

@Oxyjun
Copy link
Contributor

@Oxyjun Oxyjun commented Feb 27, 2026

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@Oxyjun Oxyjun requested a review from a team as a code owner February 27, 2026 14:46
@github-actions
Copy link
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
* @cloudflare/pcx-technical-writing

@Oxyjun Oxyjun self-assigned this Feb 27, 2026
@github-actions
Copy link
Contributor

Copy link
Collaborator

@kodster28 kodster28 left a comment

Choose a reason for hiding this comment

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

Can you walk me through the rationale behind putting these under /.opencode/skills vs /.agents/skills?

Might very well be a good reason, but I'm not versed enough to understand the distinction here.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants