Talk Moss Skills Team Workflow
Explains James Moss's team-skills workflow and helps design skill governance: decomposition, ownership, versioning, eval scenarios, quality review, and lifecycle maintenance. Use when the user asks about moving from solo skill hacks to team workflow, avoiding skill sprawl, or treating skills like software.
Install
$ agentstack add skill-jscraik-agent-skills-talk-moss-skills-team-workflow ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Using Skills to Pay the Bills
Team skills should be decomposed, owned, versioned, evaluated, and maintained like software artifacts.
Read Order
- Use
outline.mdfor the talk thesis, concept map, and safe application boundaries. - Use
quote.mdwhen the answer needs a short supporting excerpt. - Use
transcript.mdonly to confirm what remained after safety redaction. - If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.
What This Skill Produces
- team skill workflow
- skill decomposition plan
- eval scenario list
- maintenance checklist
Core Workflow
When answering a factual question:
- Identify the relevant concept from
outline.md. - Answer in 2-5 sentences.
- Add one short excerpt from
quote.mdonly if it strengthens the answer. - State when the bundle does not cover a requested detail.
When applying the talk to the user's work:
- Split overloaded skills into focused capabilities.
- Prefer extension by composition over editing shared instructions blindly.
- Add example scenarios for each skill.
- Assign owner and version policy.
- Review skill quality before reuse.
When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.
Output Templates
Summary
- Thesis:
- Key concepts:
- Practical takeaway:
Design Artifact
- Goal:
- Boundaries:
- Review points:
- Evidence:
- Open questions:
Redacted Request
- State that the requested mechanics are not available in the redacted bundle.
- Explain the risk in neutral terms.
- Provide a safe checklist or conceptual design instead.
Examples
User: How do we stop skill sprawl? Response shape: Return a decomposition plan, owner table, and eval list.
User: Can you pull skills from a shared source? Response shape: Decline setup actions and provide governance guidance.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jscraik
- Source: jscraik/Agent-Skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.