Skip to content

Comments

docs(skill): Move dotagents skill to top-level and update content#37

Merged
gricha merged 1 commit intomainfrom
skill/update-dotagents-skill
Feb 24, 2026
Merged

docs(skill): Move dotagents skill to top-level and update content#37
gricha merged 1 commit intomainfrom
skill/update-dotagents-skill

Conversation

@gricha
Copy link
Member

@gricha gricha commented Feb 24, 2026

Move the dotagents skill from plugins/dotagents/skills/ to the top-level skills/ directory and symlink it back from the plugin structure. This keeps the source of truth at the repo level rather than buried in the plugin tree.

Also updates the skill content to match the current CLI after recent PRs (#34, #35, #36):

  • Add mcp command (was completely missing from commands table and cli-reference)
  • Add positional skill args and multi-skill support to add command
  • Add --skill alias alongside --name
  • Add list --json flag
  • Fix install --force description (it bypasses the lockfile, not reinstalls)
  • Expand source formats with GitHub SSH and HTTPS URLs
  • Add hooks to Key Concepts section
  • Document interactive prompt behavior on wildcard remove
  • Add headers field to HTTP MCP example in configuration reference

Agent transcript: https://claudescope.sentry.dev/share/wmsIuw4whFWDbrLlaEhCzBR9tSiCVLSnVawOUnPYyhw

Move the dotagents skill from plugins/dotagents/skills/ to the
top-level skills/ directory, symlinking back from the plugin structure.
This keeps the source of truth at the repo level.

Updates the skill content to reflect the current CLI:
- Add mcp command to SKILL.md commands table
- Add positional skill args and multi-skill support to add command
- Add --skill alias alongside --name
- Add list --json flag to cli-reference
- Fix install --force description (lockfile bypass, not reinstall)
- Expand source formats with GitHub SSH and HTTPS URLs
- Add hooks to Key Concepts section
- Document interactive prompt on wildcard remove
- Add headers field to HTTP MCP example

Agent transcript: https://claudescope.sentry.dev/share/w9kPvHx_axMCozPnoWsnsxdJHNQnaw1JFe1crylYCXw
@vercel
Copy link

vercel bot commented Feb 24, 2026

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

Project Deployment Actions Updated (UTC)
dotagents Ready Ready Preview, Comment Feb 24, 2026 0:15am

Request Review

@gricha gricha marked this pull request as ready for review February 24, 2026 00:16
@gricha gricha merged commit f8e0df5 into main Feb 24, 2026
11 checks passed
@gricha gricha deleted the skill/update-dotagents-skill branch February 24, 2026 00:16
@@ -0,0 +1 @@
../../../skills/dotagents No newline at end of file
Copy link

Choose a reason for hiding this comment

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

Bug: The new symlink at plugins/dotagents/skills/dotagents will fail to create on standard Windows environments, causing CLI commands to crash due to permission errors.
Severity: HIGH

Suggested Fix

Implement platform-specific logic for creating symlinks. On Windows, check for permissions and consider falling back to creating a directory junction if creating a symlink fails. Add a Windows runner to the CI/CD pipeline to test this behavior.

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: plugins/dotagents/skills/dotagents#L1

Potential issue: The code uses Node.js's `fs.symlink()` API to create a symlink at
`plugins/dotagents/skills/dotagents`. This API lacks cross-platform handling and has
known issues on Windows, where creating symlinks typically requires Administrator
privileges or Developer Mode. For Windows users without these permissions, CLI commands
like `dotagents init` or `dotagents sync` will attempt to create the symlink and fail
with an `EPERM` error, causing the command to crash. The CI pipeline only runs on Linux,
so this platform-specific issue was not caught during testing.

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

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.

1 participant