@timqi/pier 0.0.8 → 0.0.15

package/skills/pier-help/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pier-help
-description: How Pier itself works — durable sessions and what survives a restart, how messages and files reach you from Slack and Telegram, in-chat commands (/stop, /settings, /bind), interrupting a running turn, and what only the operator's Console can change. Read before explaining Pier's behavior or advising a user on how to use it.
+description: How Pier itself works — durable sessions, what survives a restart, how messages and files reach you from IM, in-chat commands, and what only the operator's Console can change. Read before explaining Pier's behavior or advising a user on it.
 ---
 
 # How Pier works

package/skills/pier-slack/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pier-slack
-description: Read and write Slack through Pier's slack tool — a channel's history for a time range, one thread, posting into a thread, deleting a message Pier posted, and the Slack-specific syntax for mentions and links. Read before answering questions about Slack conversations or posting anything to a workspace.
+description: Read and write Slack through Pier's slack tool, including the Slack-specific syntax for mentions and links. Read before answering questions about Slack conversations or posting anything to a workspace.
 ---
 
 # Reading and writing Slack
@@ -97,6 +97,26 @@ Going top-level takes the explicit `"none"`: a channel's main flow is wider
 than a thread. A `thread_ts` is never inherited across a change of `channel`.
 The response carries `ts` and `threadTs` for replying under what you posted.
 
+## Editing
+
+```json
+{"operation":"edit","channel":"#ops","ts":"1717243800.000100",
+ "text":"**Deploy done** — 3 services, 1 rollback."}
+```
+
+`text` replaces the message outright; there is no partial edit. Read the
+message first if you are changing part of it.
+
+- Slack only lets Pier edit what **its own bot** posted — anyone else's message
+  answers `cant_update_message`, and the answer is to reply, not to retry.
+- `ts` is always explicit, as with `delete`, and means nothing outside the
+  channel it was read in.
+- The old text is gone — Slack keeps no version a reader can open, and may not
+  mark the message as edited at all. When the previous wording mattered to
+  people reading, say what changed rather than quietly rewriting history.
+- A long-running update — a status line, a running tally — is better as one
+  message edited in place than as a new message per change.
+
 ## Deleting
 
 ```json

package/skills/pier-tasks/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pier-tasks
-description: Delegate work to Pier subagents with the task tool — one-shot delegation, core-joined parallel fan-out, chained steps, and mid-run control (steer/resume/contact). Read before delegating to a subagent, coordinating multiple agents, or running long background work.
+description: Delegate work to Pier subagents with the task tool — one-shot, parallel fan-out, chains, mid-run control. Read before delegating to a subagent, coordinating agents, or running long background work.
 ---
 
 # Orchestrating Pier tasks
@@ -38,7 +38,7 @@ schedule policy, where `manual` means on-demand — by a human or by you.
 - The child inherits your current model unless `launch.model` is set.
   Unknown models fail with the available list in the error. `launch` applies to
   `fresh` and `fork` only — a `reuse` session owns its own model and tools.
-- The child has the same tools you do; there is no capability knob to pick.
+- The child has the same tools you do.
 - Runs time out after 900s by default; set `timeoutSeconds` in the draft for
   longer jobs.