Claude Skill

teamwork-update

Use when the user asks to inspect, install, or refresh Teamwork-owned global surfaces; do not use as a prerequisite for another skill or to migrate project documents.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download jinplu-teamwork-skills_teamwork-update-8f23dcd.zip · 2 KB

jinplu/teamwork 12 0 forks MIT Updated 9d ago

Part of jinplu/teamwork — 8 skills

Install

skills CLI npx skills add https://github.com/JinPLu/Teamwork/tree/main/skills/teamwork-update

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install jinplu-teamwork@llmmart

Git git clone https://github.com/JinPLu/Teamwork.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole jinplu/teamwork collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Teamwork Update

Update is a small install and refresh operation. It is never an automatic detour from another task.

Method

Resolve a trustworthy Teamwork package source: read ~/.teamwork/install.json root; use that path if it contains VERSION, skills/, and install.sh. If the pointer is missing or invalid, ask the user for the repository path. Do not search the home directory.
For a check-only request, run ./scripts/check-update.sh --readiness. Treat the output as diagnostic information, not permission to continue other work.
For an authorized refresh, update only the requested host. The default update target refreshes Codex; Cursor or Claude adapters require explicit targets. When refreshing an intentionally revised Agent profile, keep performance-first and cost-first distinct and compare task success, elapsed time, and cost together instead of maximizing model or effort. For a Codex profile refresh, update both the role profiles and the top-level main-thread default while preserving other user configuration: performance-first uses Terra/xhigh and cost-first uses Luna/high.
Preserve unknown and user-owned files. Replace only recognizable Teamwork-owned surfaces.
Re-run the same focused check and report what changed or the observed no-op, and any manual restart still needed.

Do not inspect or migrate project documents, compare project schemas, fetch release state, modify unrelated plugins or credentials, or require any agent to perform a readiness check. A missing specialized agent never makes Update a precondition for native work. When Update observes no change, report the observed no-op. Create or update a durable report only when that result is reusable or the user explicitly requests it.

Persistence

Persistence is optional. Write a report only when the observed result is reusable across sessions or the user explicitly requests it. When that optional checkpoint fires, write the document in the same response cycle from references/report.md at docs/teamwork/reports/<slug>.md (reuse the existing path for the same operation identity). Optional triggers: an authorized refresh completes with observed surface changes worth reusing; Update stops on a real blocker worth reusing; or a no-op result is reusable or explicitly requested. Update never blocks on a report.

Files (teamwork)

agents

openai.yaml 216 B

interface:
  display_name: "Teamwork Update"
  short_description: "Check and refresh the global Teamwork installation"
  default_prompt: "Use $teamwork-update to inspect or refresh this Codex Teamwork installation."

references

report.md 1.1 KB

---
status: active
superseded-by:
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
---

# Report: <subject>

## Current synthesis

<requested outcome and directly observed result; label it complete, partial,
unobserved, or blocked only as certified by the result owner>

## Identity and request

- Subject identity: <stable continuing objective or operation>
- Authoritative owner: <result owner>
- Requested outcome and scope: <authorized requested result>

## Observed outcome and completion boundary

<only what was directly observed; include the success signal, observation
method, and scope for any completion claim>

## Decisive evidence

<evidence supporting the observed outcome>

## Resulting state and material changes

<current state and material changes, not an activity log>

## Remaining action, blocker, and nonclaims

<smallest remaining action, exact blocker, or none observed; state any material
completion, release, activation, or real-runtime result that is not supported>

## History

<Append only. Never rewrite or remove; a correction is a new dated entry.>

### <date/time — semantic change>

<result-state delta, not an activity log>

SKILL.md 2.5 KB

---
name: teamwork-update
description: Use when the user asks to inspect, install, or refresh Teamwork-owned global surfaces; do not use as a prerequisite for another skill or to migrate project documents.
---

# Teamwork Update

Update is a small install and refresh operation. It is never an automatic detour
from another task.

## Method

1. Resolve a trustworthy Teamwork package source: read
   `~/.teamwork/install.json` `root`; use that path if it contains `VERSION`,
   `skills/`, and `install.sh`. If the pointer is missing or invalid, ask the
   user for the repository path. Do not search the home directory.
2. For a check-only request, run `./scripts/check-update.sh --readiness`. Treat
   the output as diagnostic information, not permission to continue other work.
3. For an authorized refresh, update only the requested host. The default
   `update` target refreshes Codex; Cursor or Claude adapters require explicit
   targets.
   When refreshing an intentionally revised Agent profile, keep
   `performance-first` and `cost-first` distinct and compare task success,
   elapsed time, and cost together instead of maximizing model or effort.
   For a Codex profile refresh, update both the role profiles and the
   top-level main-thread default while preserving other user configuration:
   `performance-first` uses Terra/xhigh and `cost-first` uses Luna/high.
4. Preserve unknown and user-owned files. Replace only recognizable
   Teamwork-owned surfaces.
5. Re-run the same focused check and report what changed or the observed no-op,
   and any manual restart still needed.

Do not inspect or migrate project documents, compare project schemas, fetch
release state, modify unrelated plugins or credentials, or require any agent to
perform a readiness check. A missing specialized agent never makes Update a
precondition for native work. When Update observes no change, report the
observed no-op. Create or update a durable report only when that result is
reusable or the user explicitly requests it.

## Persistence

Persistence is optional. Write a report only when the observed result is reusable
across sessions or the user explicitly requests it. When that optional
checkpoint fires, write the document in the same response cycle from
`references/report.md` at
`docs/teamwork/reports/<slug>.md` (reuse the existing path for the
same operation identity). Optional triggers: an authorized refresh completes
with observed surface changes worth reusing; Update stops on a real blocker
worth reusing; or a no-op result is reusable or explicitly requested.
Update never blocks on a report.