opencode-tandem 0.6.2 → 0.6.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +2 -0
  2. package/package.json +1 -1
  3. package/prompt.md +8 -0
package/README.md CHANGED
@@ -52,6 +52,8 @@ The plugin notices which CLI tools are actually installed on your machine, and f
52
52
  - `pandoc` - convert docx/odt/rtf to markdown
53
53
  - `osascript` (macOS only) - drive the user's real browser sessions via AppleScript
54
54
  - `jira`, `aws`, `saml2aws` - if your workflow includes them
55
+ - `gcx` (Grafana CLI) - query Grafana logs and metrics from the terminal
56
+ - `slackcli` (`brew install shaharia-lab/tap/slackcli`) - read Slack channels, DMs and threads from the terminal
55
57
  - `tmux` or `paseo` - run the main session inside one of these to enable [interactive subagents](#interactive-subagents)
56
58
 
57
59
  ## Attribution
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-tandem",
3
- "version": "0.6.2",
3
+ "version": "0.6.4",
4
4
  "description": "Shared agent system prompt and skills for OpenCode, from the tandem-skills repo",
5
5
  "keywords": [
6
6
  "opencode",
package/prompt.md CHANGED
@@ -48,6 +48,14 @@ A number of CLI tools are installed on this laptop and fully authenticated, you'
48
48
  <!--cli:jira-->
49
49
  - Use `jira` for anything Jira related, including searching for and reading tickets and comments, as well as creating and updating tickets and comments under them
50
50
  <!--/cli-->
51
+ <!--cli:gcx-->
52
+ - Use `gcx` to query Grafana logs and metrics: `gcx logs query '<logql>' --since 1h`, `gcx metrics query '<promql>' --since 1h`
53
+ - Use the `--jq '<expr>'` flag to filter or reshape gcx JSON output
54
+ <!--/cli-->
55
+ <!--cli:slackcli-->
56
+ - Use `slackcli` to read Slack: `slackcli conversations read <channel-or-slack-url>`, `slackcli search messages '<query>'`; add `--json` when you process the output
57
+ - Always include the message permalink, so the user can open and reply to it in Slack
58
+ <!--/cli-->
51
59
  <!--cli:aws-->
52
60
  - Use `aws` when you need to check what's happening in AWS accounts
53
61
  - When using AWS CLI always pass --profile and --region explicitly. The profile is usually clear from context - if it is not, ask, never guess