Update skills and add scripts and prompts to keep skills up to date

[simon-johansson]

I added some scripts and prompts we can run to update the skills when the docs gets updated. These prompts should probably run for the llm-instructions.txt as well but that is not in this repo so.... figure that out later.

[ivancernja]

@simon-johansson I'm not sure whether it's the best approach to use prompts in favor of scripts due to accuracy. I've had experience in the past with a similar prompt-based approach when I had to fix broken links in certain pages which I did by telling the LLM to run the contents against a sitemap and to ensure that all of the links are valid and exist - but that worked only once out of a couple of times.

Few questions:

1. How did your testing go with the prompt-based approach?
2. Who is the target person that will be running these scripts?
3. Should we hook these up to trigger any time we push updates to the docs? What's the UX here?

Other than that, looks great - much cleaner and efficient than the instructions we have now.

[simon-johansson]

Good questions @ivancernja, sorry for not being more clear.

• How did your testing go with the prompt-based approach?

Quite good. It is of course not deterministic and I don't expect the AI to be perfect in suggesting what skills to update but I think this is a good complement to updating the skills by hand.

• Who is the target person that will be running these scripts?

It's only for us internally. So when we have done some changes to the docs I think we can run the prompts to get some guidance in what skills needs to be updated.

• Should we hook these up to trigger any time we push updates to the docs? What's the UX here?

I don't think we need to make it automatic. I think it's good enough to run the prompts manually. The prompts will help when updating the skills, which we will need to do anyway.

[ivancernja]

Thanks @simon-johansson.

It's only for us internally. So when we have done some changes to the docs I think we can run the prompts to get some guidance in what skills needs to be updated.

I don't think we need to make it automatic. I think it's good enough to run the prompts manually. The prompts will help when updating the skills, which we will need to do anyway.

My only concern here is that the skills repository is public and we accept external contributions. Since the prompts and scripts reference internal workflows ("for us internally"), it might not be clear to outside contributors how they fit into the maintenance process or whether they should use them when proposing updates.

This makes me wonder if we should reconsider whether the repo should remain public, or if we're actually seeing value from external contributions that justifies keeping it open. If it's primarily an internal tool, we might want to make it private to avoid confusion.

[simon-johansson]

Updated the PR to remove the prompts and the scripts.
Might need to update the skills version before merging

[ivancernja]

Suggested change

	1. Run the `update-docs-summaries-prompt.md` using Claude Code prompt to update the `ts-docs-summary.md`, `go-docs-summary.md`, and `platform-docs-summary.md` files.
	1. Run the `update-docs-summaries-prompt.md` prompt using Claude Code to update the `ts-docs-summary.md`, `go-docs-summary.md`, and `platform-docs-summary.md` files.