Skip to content
Back to skills

Core Constraint

ASecurity

Sub-skill of agent-teams: Core Constraint.

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 9, 2026
ai-agentsgogit

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add vamseeachanta/workspace-hub --skill core-constraint --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Core Constraint?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Core Constraint
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vamseeachanta-core-constraint-workspace-hub/badge)](https://www.skillsdirectory.com/skills/vamseeachanta-core-constraint-workspace-hub)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-teams-core-constraint
description: 'Sub-skill of agent-teams: Core Constraint.'
version: 1.0.0
category: workspace-hub
type: reference
scripts_exempt: true
---

# Core Constraint

## Core Constraint


```
MAX_TEAMMATES = 10  (set in .claude/settings.json — git-tracked)
Recommended sweet spot: 2–3 teammates for this workspace's workload
```

Default to **fewer agents**, not more. Spawn only as many as strictly needed.
Coordination overhead grows quadratically; benefits only appear when tasks are
truly parallel and long-running.

`MAX_TEAMMATES=10` is a ceiling, not a target. The realistic effective range
for workspace-hub engineering work is **2–3 teammates**. Raising it above that
adds token cost with diminishing returns given the predominantly sequential
solver-pipeline nature of the work.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…