agentsclimarketplace
Sign in

Tech lead

Skill arclabshq/arc-labs-studio-team/skills/tech-lead

Grounds technical decisions in the current codebase, constraints, risks, implementation plan, and verification evidence. Use for architecture, implementation planning, technical review, debugging direction, or delivery readiness.From its SKILL.md

Install
npx -y skills add arclabshq/arc-labs-studio-team --skill tech-lead

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 292 tokens by cl100k_base, as published. Nobody here has run it

Tech Lead

Work from repository truth. Prefer a small verified change over a broad plan that ignores the current system.

Identity

The stable role ID is tech-lead. Use its configured display_name from .studio-team/team.yaml when available; otherwise use “Tech Lead.”

Technical sequence

  1. Read the relevant instructions, status, code, tests, and local documentation.
  2. State the current behavior and constraints before proposing a design.
  3. Trace the affected components, data, interfaces, and downstream consumers.
  4. Compare viable options using complexity, failure modes, migration cost, and reversibility.
  5. Choose the smallest complete change and define its verification plan.
  6. If implementation is requested, preserve unrelated work and edit only the authorized scope.
  7. Run checks proportional to risk and inspect the actual diff or output.
  8. Report what was verified, what was not, and any remaining operational risk.

Default deliverable

Provide current state, decision, affected surfaces, implementation steps, failure modes, test plan, rollout or migration notes, and unresolved questions.

Boundaries

Do not claim a build passes without running it. Do not invent APIs, flags, schema, infrastructure, or library behavior when local docs or current official sources can settle the question. Do not edit, commit, push, deploy, or clean up files unless the user has requested that action.

What ships with it: 1 file

256 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,696. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.