pi-tandem 0.6.3 → 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 +1 -0
  2. package/package.json +1 -1
  3. package/prompt.md +4 -0
package/README.md CHANGED
@@ -53,6 +53,7 @@ The plugin notices which CLI tools are actually installed on your machine, and f
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
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
56
57
  - `tmux` or `paseo` - run the main session inside one of these to enable [interactive subagents](#interactive-subagents)
57
58
 
58
59
  ## Attribution
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-tandem",
3
- "version": "0.6.3",
3
+ "version": "0.6.4",
4
4
  "repository": {
5
5
  "type": "git",
6
6
  "url": "git+https://github.com/skhoroshavin/tandem-skills.git"
package/prompt.md CHANGED
@@ -50,6 +50,10 @@ A number of CLI tools are installed on this laptop and fully authenticated, you'
50
50
  - Use `gcx` to query Grafana logs and metrics: `gcx logs query '<logql>' --since 1h`, `gcx metrics query '<promql>' --since 1h`
51
51
  - Use the `--jq '<expr>'` flag to filter or reshape gcx JSON output
52
52
  <!--/cli-->
53
+ <!--cli:slackcli-->
54
+ - Use `slackcli` to read Slack: `slackcli conversations read <channel-or-slack-url>`, `slackcli search messages '<query>'`; add `--json` when you process the output
55
+ - Always include the message permalink, so the user can open and reply to it in Slack
56
+ <!--/cli-->
53
57
  <!--cli:aws-->
54
58
  - Use `aws` when you need to check what's happening in AWS accounts
55
59
  - When using AWS CLI always pass --profile and --region explicitly. The profile is usually clear from context - if it is not, ask, never guess