agent-teams-workspace-work-profile-updated-2026-03-10
Sub-skill of agent-teams: Workspace Work Profile (Updated 2026-03-10).
Best use case
agent-teams-workspace-work-profile-updated-2026-03-10 is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of agent-teams: Workspace Work Profile (Updated 2026-03-10).
Teams using agent-teams-workspace-work-profile-updated-2026-03-10 should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workspace-work-profile-updated-2026-03-10/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-teams-workspace-work-profile-updated-2026-03-10 Compares
| Feature / Agent | agent-teams-workspace-work-profile-updated-2026-03-10 | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of agent-teams: Workspace Work Profile (Updated 2026-03-10).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Workspace Work Profile (Updated 2026-03-10) ## Workspace Work Profile (Updated 2026-03-10) This workspace is **engineering-heavy with sequential solver pipelines**. Most work does NOT benefit from teams. Use this table before spawning: | Work Type | Team Useful? | Notes | |-----------|-------------|-------| | OrcaWave/AQWA solver runs | **No** | Sequential: mesh → solve → validate → report | | WRK item staged pipeline | **No** | Each stage depends on previous stage output | | Cross-review (Codex/Codex/Gemini) | **No** | Already scripted via `cross-review.sh` | | L01–L06 validation cases | **Maybe** | Cases are independent — 2-3 agents viable | | Multi-repo exploration | **Maybe** | Parallel file reads across submodules | | Documentation/reporting | **No** | Single-pass generation | | Bulk transforms (50+ files) | **Yes** | One agent per batch | **Key insight**: The biggest efficiency gain in this workspace comes from **better WRK scoping** (1-2 goals per session), not from parallelising with teams. Use teams only when tasks are genuinely independent AND > 20 min each.
Related Skills
agent-os-framework
Generate standardized .agent-os directory structure with product documentation, mission, tech-stack, roadmap, and decision records. Enables AI-native workflows.
teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
solidworks-to-blender-pipeline
Use when converting SolidWorks .sldprt/.sldasm geometry to Blender for rendering, animation, or visualization, including questions about STEP export settings, FreeCAD as a bridge, or which mesh format (STL/OBJ/GLTF) to choose.
digitalmodel-worktree-test-execution-with-shared-venv
Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.
digitalmodel-orcawave-orcaflex-proof-workflows
Class-level digitalmodel OrcaWave/OrcaFlex readiness, semantic-proof, fixture-proof, and closeout workflows.
blender-worktree-test-hardening
Recover and harden digitalmodel Blender automation work in isolated worktrees when uv/editable dependency paths break and local machines lack a Blender executable.
worktree-pre-push-bypass-for-tier1-checks
Handle workspace-hub integration-branch pushes from isolated git worktrees when the pre-push hook incorrectly assumes sibling tier-1 repos exist under the worktree path.
worktree-branch-sync-hygiene
Class-level branch, worktree, dirty-main, stash, sync, and hook hygiene for workspace-hub style multi-repo work.
workspace-knowledge-doc-contracts
Class-level workspace knowledge, LLM-wiki, repo mission contracts, stale doc references, semantic taxonomy, and knowledge-source reconnaissance.
workspace-hub-overnight-plan-monitor
Monitor and reconcile workspace-hub overnight planning or implementation batches, including process status, result artifacts, issue/commit verification, and controlled failed-lane recovery.
verify-Codex-run-commit-vs-working-tree-before-closing
After a Codex implementation run, verify the claimed file set against the actual commit and working tree before treating the issue as fully complete.
work-around-merge-conflicts-in-test-execution
Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly