Hi 👋, thanks for sharing the agentic collections, I appreciate that
since local and internal models are quite powerful today, I see a valid use-case especially for the skills involving
- troubleshooting, example rh-basic/skills/red-hat-diagnostics/SKILL.md (not uploading but collecting data, investigating locally)
- debugging, example rh-developer/skills/debug-pod/SKILL.md
for skills like that i would like those to work locally in air-gapped environments. However, as I read it, the first example will for instance create AND upload diagnostics. In air gapped environments, we really want this being a two-step skill: One to create and collect diagnostics for local-only investigation, and one for sharing with Redhat.
I might be misunderstanding, but some of the skills (not all) require online access, to mcp servers etc.
Do you consider that offline scenario into how you design skills for this repository?
Hi 👋, thanks for sharing the agentic collections, I appreciate that
since local and internal models are quite powerful today, I see a valid use-case especially for the skills involving
for skills like that i would like those to work locally in air-gapped environments. However, as I read it, the first example will for instance create AND upload diagnostics. In air gapped environments, we really want this being a two-step skill: One to create and collect diagnostics for local-only investigation, and one for sharing with Redhat.
I might be misunderstanding, but some of the skills (not all) require online access, to mcp servers etc.
Do you consider that offline scenario into how you design skills for this repository?