OBSINTA-1609: cluster-troubleshoot skill rename tools to scripts - #46
OBSINTA-1609: cluster-troubleshoot skill rename tools to scripts#46tremes wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tremes The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
@tremes: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/verified by @tremes manually |
|
@tremes: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@tremes: This pull request references OBSINTA-1609 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/override ci/prow/eval |
|
@tremes: tremes unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
|
||
| # Tools | ||
|
|
||
| A `tools/` directory is colocated with this SKILL.md file. **Do not assume `tools/` is relative to the working directory.** Use the absolute path based on where you read this file from — for example, if you read this file from `/app/skills/investigate-alert/SKILL.md`, the tools are at `/app/skills/investigate-alert/tools/`. |
There was a problem hiding this comment.
You wouldn't need this at all if you adhered to the Agent Skills spec and used scripts/ instead. Models will find it more familiar.
There was a problem hiding this comment.
There was a problem hiding this comment.
I am also curious if there's any evidence these tools are useful, the latest models understand how to debug a kubernetes cluster without this information. Perhaps it is helpful to smaller models.
There was a problem hiding this comment.
Thank you! I didn't know about this. I am going to update.
I think it's still useful since there's no MCP or skill as far as I know defining the communication with Prometheus & Alertmanager.
Signed-off-by: Tomáš Remeš <tremes@redhat.com>
bbdcbf1 to
cf0e842
Compare
|
@tremes: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@tremes: This pull request references OBSINTA-1609 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.1.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
/override ci/prow/eval |
|
@Cali0707: Overrode contexts on behalf of Cali0707: ci/prow/eval DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@tremes: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
The agent assumed tools/ was relative to the working directory (/app), but the scripts are mounted inside the skill directory. This caused nondeterministic code 127 failures during analysis. Add explicit guidance to resolve tool paths relative to the SKILL.md location.
Assisted-by: Claude Code:claude-opus-4-6