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

feat: ship skills/elastic/SKILL.md for agent invocation

Open Beginner friendly
  • Is something wrong?
#628 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
cli, documentation

Research direction

Read AGENTS.md and the existing .claude/skills/ guidance, then inspect the README and use elastic --help --json or elastic cli-schema to verify the documented commands and options. Add skills/elastic/SKILL.md with the listed agent workflow and link it from the README; done means an agent can configure a context and run a read command from the skill alone.

Written by the indexing model from the issue text.

Description

enhancement

AGENTS.md is for contributors and cli-schema is for introspection. Nothing in-repo tells an agent host how to run elastic. Contributor skills under .claude/skills/ cover build and test only.

Add skills/elastic/SKILL.md (agentskills.io format) covering:

  • Interactivity: never prompt; pass --yes; --dry-run before mutations
  • Prefer --json; discover inputs with --help --json or elastic cli-schema
  • Target a context with --use-context; do not pass credentials as flags
  • Config / env: ELASTIC_CLI_CONFIG_FILE, ELASTIC_CLI_TELEMETRY, ELASTIC_NO_BANNER, NO_COLOR
  • Diagnose with elastic status --json before retrying a failed API call
  • Destructive confirm: confirmation_required means add --yes
  • Do not dump docs/cli/schema.json into context; query the command you need

No elastic skill install command. Markdown in-repo plus a README pointer is enough for MVP.

Acceptance: one SKILL.md, linked from the README. An agent can configure a context and run a read command from the skill alone.

Dominant language
TypeScript
Stars
43
Forks
24
Avg merge
1d 5h
Merged PRs (30d)
63

Getting set up

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 elastic/cli

All issues in elastic/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.