crewx-pi-kit 0.1.6 → 0.1.7

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 -1
  2. package/package.json +1 -1
  3. package/skills/crew-workflow/SKILL.md +3 -2
package/README.md CHANGED
@@ -10,7 +10,7 @@ work, safety boundaries, and agent handoffs.
10
10
  Install it with Pi:
11
11
 
12
12
  ```sh
13
- pi install npm:crewx-pi-kit@0.1.6
13
+ pi install npm:crewx-pi-kit@0.1.7
14
14
  ```
15
15
 
16
16
  CrewX injects short-lived `CREWX_URL` and `CREWX_TOKEN` capabilities only while
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "crewx-pi-kit",
3
- "version": "0.1.6",
3
+ "version": "0.1.7",
4
4
  "description": "Typed CrewX tools and operating skills for managed Pi agents.",
5
5
  "type": "module",
6
6
  "files": [
package/skills/crew-workflow/SKILL.md CHANGED
@@ -10,5 +10,6 @@ description: Complete a CrewX assignment as a dependable team member. Use for ev
10
10
  3. Use the smallest capable tool. Prefer CrewX tools for memory, tasks, documents, integrations, and email; use the managed browser or desktop only when visual or authenticated interaction is required.
11
11
  4. Verify meaningful state changes from observable results. A click, submitted command, or drafted email is not proof of completion.
12
12
  5. Keep email, publishing, purchases, deletions, access changes, and other consequential actions behind their required human approval boundary.
13
- 6. End with one concise user-facing answer: outcome first, important evidence or blockers second, and the next required action only when one remains. Do not concatenate planning notes, tool-call narration, hidden reasoning, or repeated progress updates into the final answer; CrewX records safe work activity separately.
14
- 7. Save only durable, verified learnings to team memory. Update a CrewX task or shared document when the assignment requires a lasting work product or status change.
13
+ 6. Do not end the run on an intention. If you say you will start, check, open, create, or continue something, take that action in the same run. When the next step requires a person, use the appropriate CrewX access request or computer handover tool before replying. When completion is impossible, report the verified blocker plainly instead of implying that work will continue after the run ends.
14
+ 7. End with one concise user-facing answer: outcome first, important evidence or blockers second, and the next required action only when one remains. Do not concatenate planning notes, tool-call narration, hidden reasoning, or repeated progress updates into the final answer; CrewX records safe work activity separately.
15
+ 8. Save only durable, verified learnings to team memory. Update a CrewX task or shared document when the assignment requires a lasting work product or status change.