Auto generate skill for agent-skills-sandbox repo

[tehbooom]

Auto generates a skill to put in elastic/agent-skills-sandbox repo

Will need to discuss if this fits here or if we would like to have another repo pull in the providers to generate and then push to that repo.

Note

Add skill generator CLI for the elasticstack-terraform agent-skills-sandbox repo

• Adds a Go CLI at scripts/generate-skill that produces a deterministic skill directory tree under dist/skill/ by combining hand-authored assets and provider docs.
• Scans docs/resources and docs/data-sources, parses frontmatter, and merges entities into a generated references/index.md with descriptions and file links.
• Copies static assets (including SKILL.md and reference docs) into the output tree, substituting {{VERSION}} with the value passed via --provider-version.
• Writes a GENERATED.md provenance file summarising entity counts and provider version.
• Adds make skill-generate and make skill-test targets to invoke the generator and its unit tests respectively.

^{Macroscope summarized 6f18ed1.}

[github-actions]

❌ PR Changelog Check failed

The following issues were found with the ## Changelog section:

• No ## Changelog section found in PR body

Expected format

## Changelog
Customer impact: <none|fix|enhancement|breaking>
Summary: <one-line description>  (required when Customer impact is not "none")

### Breaking changes
<free-form markdown>  (required when Customer impact is "breaking")

Or add the no-changelog label to bypass this check.

[macroscopeapp]

🟢 Low references/provider.md:38

The Kibana auth environment variables table at line 38 omits KIBANA_BEARER_TOKEN, which is a supported authentication mechanism per the provider implementation. Since this document is used to generate AI skills, the missing token type means generated skills will never suggest bearer token authentication for Kibana even when it is valid.

-| Kibana | `KIBANA_ENDPOINT` | `KIBANA_USERNAME` + `KIBANA_PASSWORD`, or `KIBANA_API_KEY` |
+| Kibana | `KIBANA_ENDPOINT` | `KIBANA_USERNAME` + `KIBANA_PASSWORD`, or `KIBANA_API_KEY`, or `KIBANA_BEARER_TOKEN` |

🤖 Copy this AI Prompt to have your agent fix this:

In file scripts/generate-skill/assets/references/provider.md around line 38:

The Kibana auth environment variables table at line 38 omits `KIBANA_BEARER_TOKEN`, which is a supported authentication mechanism per the provider implementation. Since this document is used to generate AI skills, the missing token type means generated skills will never suggest bearer token authentication for Kibana even when it is valid.

[tobio]

I'm curious what this solves over one of:

• Referencing https://registry.terraform.io/providers/elastic/elasticstack/latest/docs
• Embedding the docs directory (well formed, generated from the implementation so no chance of drift)

I suppose referencing HTTP docs in a skill might be less effective than sourcing local content, but basing this off the generated docs feels like a better path (they're for the right audience, where the specs are more developer focused).

[tehbooom]

I'm curious what this solves over one of:

• Referencing https://registry.terraform.io/providers/elastic/elasticstack/latest/docs
• Embedding the docs directory (well formed, generated from the implementation so no chance of drift)

I suppose referencing HTTP docs in a skill might be less effective than sourcing local content, but basing this off the generated docs feels like a better path (they're for the right audience, where the specs are more developer focused).

You're right using the docs directory is better than the specs