Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Addition Proposal: Add a CLI Skill for Agents

Open
#47 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
ai, cli

Research direction

No file, test, or entry point is named. Start by mapping the existing TypeScript CLI command surface, then clarify the scope of an agent skill and an environment-controlled read-only mode; done should include agreed acceptance criteria for both proposals.

Written by the indexing model from the issue text.

Description

I think making a skill for Ai Agents to use the dokploy cli is worthwhile.

The MCP bloats the context window too much, even with the new minimal env var or specific tools enabled, it's still costly.

I tried setting up the MCP with Cloudflare MCP Portals with Code Mode as I have other MCP's setup there too (Would be an ideal efficient deployment in my opinion) but that had too much friction to setup. So I dropped the idea for now.

The cli took me a few minutes to setup, it works. A skill to along with this would be a much more efficient way to let Ai Agents manage your instance.

Additionally a setting to toggle or restrict it to read only mode would be nice too (Ideally via some env variable so the Ai Agent can't get around it as easily)

Imo using the MCP more optimally would require a bunch of changes and I think the CLI route would be easier to use as a global low friction option. Not sure if others would agree.

Dominant language
TypeScript
Stars
152
Forks
46
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Dokploy/cli

All issues in Dokploy/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.