Run any Skill in Manus with one click

teamwork-update

Stars8

Forks0

UpdatedJuly 25, 2026 at 01:58

Use when the user asks to check, install, activate, repair, or refresh globally installed Teamwork skills, agents, managed policy, routing, or notifications; do not use for project-local instructions, memory, CodeGraph context, source release publication, or unrelated plugins and tools.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

JinPLu

JinPLu/Teamwork

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	teamwork-update
description	Use when the user asks to check, install, activate, repair, or refresh globally installed Teamwork skills, agents, managed policy, routing, or notifications; do not use for project-local instructions, memory, CodeGraph context, source release publication, or unrelated plugins and tools.

Teamwork Update

Check or refresh Teamwork-managed global installation surfaces only. Never rewrite project context as part of an update. Ordinary natural discussion or brainstorming does not activate Update unless the existing global-install outcome trigger applies.

Resolve The Package

Do not assume the current directory is a Teamwork checkout. From Marketplace, resolve the package root with package-owned scripts/plugin-runtime-root.py, two levels above this skill, then use that root's scripts/check-update.sh and install.sh. From a checkout, use the verified repo root. If plugin-runtime-root.py is missing, also check $TEAMWORK_ROOT or ~/.cursor/.teamwork-mcp.json; otherwise report missing source instead of searching or modifying arbitrary directories.

Check Or Refresh

Dispatch Explorer to run resolved scripts/check-update.sh --plugin for Marketplace, or scripts/check-update.sh for a checkout. Freshness checks are read-only and stop after an evidence-backed status report.
For explicit install, activate, repair, or update, explain managed global surfaces and preserve detected profile/notification choice. Follow the checker's safe command; do not invent profile or destination.
First activation that would add global agents, policy, routing, or notifications requires explicit effect authority. An explicit request to perform that activation supplies it; a request merely asking what is stale does not. Root alone asks users through the current host's native surface; leaf roles return proposed questions or blockers to Root. Ask only for missing mutation authority or unavoidable manual host action. Answers do not expand authority.
Dispatch Worker only for transferable, precisely owned refresh actions. Credentials, host UI, trust, notification approval, and privileged surfaces remain with Root and require exact effect authority. Refresh only verified Teamwork-owned files. Preserve unrelated/unknown files. If cleanup cannot distinguish owned files from user content, stop and name the conflict.
Dispatch Explorer to rerun the same checker with --readiness after changes; pass both --plugin and --readiness for Marketplace. Static file freshness is not proof of live host activation; report required restart, policy paste, notification review, or other human action separately.

A check-only Update remains read-only and conversational. After a mutating Update in an initialized writable project, a receipt is a completion companion and defaults through Writer unless the user says no files, off-record, read-only, no writes, or equivalent. Freeze a bounded receipt packet: purpose/audience, facts/sources, frozen decision/status, style/structure, artifact kind/consumer, preserve/forbid, managed surfaces, freshness evidence, validation, and manual actions. Dispatch one low-cost Writer; Root may do only answer-invariant handoff work while Writer runs and must join and read back before claiming the receipt is saved or durable. Writer uses artifact-inspect -> artifact-schema <create|update|supersede> -> artifact-apply; the transaction derives the destination and registers the ordinary index. Writer is disposable compute and the transaction owns destination, compare-and-swap, journal recovery, atomic apply, and readback. If interrupted before generic artifact apply begins, there is no durable claim; recover only from surviving workflow evidence or report unsaved. Missing project memory, Writer, brief, authority, consumer, or transaction blocks only persistence: deliver the receipt and report it unsaved/blocked. No Root or Worker fallback writes it.

For notifications, trust only the specific Teamwork hooks reported by the package; never enable trust-all. Do not install external dependencies, MCP servers, paid services, unrelated plugins, or credentials without separate authority.

This skill does not edit VERSION, manifests, changelogs, commits, tags, or GitHub Releases. It does not pull or publish source without explicit repository authority. It never runs project initialization or edits project instruction and memory files. Finish with source and installed versions, profile, each managed surface's freshness, activation strength, manual actions, and unresolved drift.

More from this repository

same repository

grill-me

JinPLu/Teamwork

Use when a proposed change has major external impact or the user explicitly asks to be grilled, stress-tested, questioned before action, or to save or resume a Grill discussion; do not use for ordinary clarification, settled trade-offs, mechanical details, negative intent, quoted examples, or maintenance.

2026-07-258

teamwork-debug

JinPLu/Teamwork

Use when a failure, crash, flake, regression, or unexpected result has an unknown cause that prevents a safe fix; do not use when the cause and narrow fix are already clear, for general fact finding or design, or when the user asks only for review.

2026-07-258

teamwork-design

JinPLu/Teamwork

Use when the user asks to design, architect, choose an approach, or resolve a material product, workflow, API, or system trade-off before implementation and the direction is not yet settled; choose standard or adversarial search from the request and evidence; do not use for discussion-only brainstorming, external fact lookup alone, unknown-cause failures, a plan for an already chosen direction, clear implementation, or review.

2026-07-258

teamwork-explore

JinPLu/Teamwork

Use when the requested result is direct evidence about local code, files, configuration, logs, tests, history, artifacts, or runtime state; do not use for external or current-source research, ordinary local reads needed during implementation, unknown-cause diagnosis, design, or mutation.

2026-07-258

teamwork-goal

JinPLu/Teamwork

Use when the user explicitly asks the host to keep working until a verifiable result, fix until green, converge without stopping, monitor through completion, or operate within a stated budget; do not use for ordinary one-shot work or infer persistence from task difficulty.

2026-07-258

teamwork-init

JinPLu/Teamwork

Use when the user asks to initialize, audit, repair, migrate, or slim project-local AI instructions, Teamwork context or memory, project routing, or local CodeGraph policy inside a named project; do not use for global skill, agent, policy, notification, plugin, or host installation and refresh.

2026-07-258

name	teamwork-update
description	Use when the user asks to check, install, activate, repair, or refresh globally installed Teamwork skills, agents, managed policy, routing, or notifications; do not use for project-local instructions, memory, CodeGraph context, source release publication, or unrelated plugins and tools.

Teamwork Update

Resolve The Package

Check Or Refresh

Dispatch Explorer to run resolved scripts/check-update.sh --plugin for Marketplace, or scripts/check-update.sh for a checkout. Freshness checks are read-only and stop after an evidence-backed status report.
For explicit install, activate, repair, or update, explain managed global surfaces and preserve detected profile/notification choice. Follow the checker's safe command; do not invent profile or destination.
First activation that would add global agents, policy, routing, or notifications requires explicit effect authority. An explicit request to perform that activation supplies it; a request merely asking what is stale does not. Root alone asks users through the current host's native surface; leaf roles return proposed questions or blockers to Root. Ask only for missing mutation authority or unavoidable manual host action. Answers do not expand authority.
Dispatch Worker only for transferable, precisely owned refresh actions. Credentials, host UI, trust, notification approval, and privileged surfaces remain with Root and require exact effect authority. Refresh only verified Teamwork-owned files. Preserve unrelated/unknown files. If cleanup cannot distinguish owned files from user content, stop and name the conflict.
Dispatch Explorer to rerun the same checker with --readiness after changes; pass both --plugin and --readiness for Marketplace. Static file freshness is not proof of live host activation; report required restart, policy paste, notification review, or other human action separately.