Skip to content

sandbaseai/sandbase-skills / marketing/team-composition-analysis

team-composition-analysis

Verified

Create or review team composition analysis deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for team composition analysis planning or analysis.

Team Composition Analysis

Use this Skill to produce a bounded, verifiable Team Composition Analysis outcome. Preserve the user's chosen stack, source material, and authorization boundaries.

Read the SandBase API map only when the task genuinely needs an external data source or generative model.

Workflow

  1. Inspect the available files, runtime, versions, inputs, and existing conventions before deciding what to change.
  2. Restate the requested outcome, constraints, acceptance checks, and any assumption that could change the result.
  3. Produce the smallest complete implementation, analysis, or artifact that satisfies those checks.
  4. Verify the real output with appropriate tests, previews, calculations, or source comparison; do not infer success from file creation alone.
  5. Return the deliverable, evidence of validation, material assumptions, and unresolved limitations.

Quality gates

  • State the objective, decision owner, horizon, inputs, constraints, and definitions before analyzing.
  • Show formulas, assumptions, ranges, and scenarios so another reviewer can reproduce the conclusion.
  • Separate observations, judgments, actions, owners, and dates; escalate legal, tax, accounting, or policy ambiguity.

Focus checks

  • Tie roles and sequencing to company stage, goals, capability gaps, budget, management capacity, and location; present compensation or equity as sourced ranges requiring local review.

SandBase boundary

Keep the core Team Composition Analysis work local. Use SandBase only for current external evidence, search, scraping, enrichment, or model inference that is not already available through the user's authorized tools.

  1. Call sandbase_discover with a short capability query.
  2. Call sandbase_inspect for viable candidates and compare the live schema, coverage, limits, output, execution mode, and price.
  3. Prefer a dedicated tool or API the user already has. Send only the minimum necessary data.
  4. Before any paid call, show the endpoint, important arguments, current unit price, call count, and total estimate or uncertainty, then obtain confirmation.
  5. Use sandbase_account before an approved multi-call batch and call sandbase_run only with current schema-defined arguments.
  6. Poll asynchronous work with sandbase_run_get using the same run ID; never resubmit merely because it is pending.
  7. Use sandbase_runs only to recover status or reconcile observed cost.

If SandBase is unavailable, continue with local work and authorized sources when possible. Do not silently switch providers, fabricate external results, or claim a generation or retrieval succeeded.

Handoff

Provide the completed artifact or findings, concise reproduction steps, checks actually run, source or asset provenance, SandBase endpoint and run IDs when used, observed cost when available, and any follow-up that still requires user action.

planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall