agentsclimarketplace

Do work

Skill mappa-ai/skills/utils-skills/do-work

Agent skill for integrating Mappa Conduit SDKs in TypeScript, Python, Go, and Rust. Guides first-time setup with media upload, speaker targeting, webhook-first report flows, and documented Conduit APIs for Claude Code and other agentic coding tools.

Install
npx -y skills add mappa-ai/skills --skill do-work

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 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.

What its author says it does

Copied from the file, not written here

Execute a unit of work end-to-end: plan, implement, validate with typecheck and tests, then commit. Use when user wants to do work, build a feature, fix a bug, or implement a phase from a plan.

SKILL.md

1.4 KB, as published. Nobody here has run it

Do Work

Execute a complete unit of work: plan it, build it, validate it, commit it.

Workflow

1. Understand the task

Read any referenced plan or PRD. Explore the codebase to understand the relevant files, patterns, and conventions. If the task is ambiguous, ask the user to clarify scope before proceeding.

2. Plan the implementation (optional)

If the task has not already been planned, create a plan for it.

3. Implement

For backend code: use red/green/refactor, one test at a time in a tracer-bullet style.

  1. Write a single failing test for the smallest vertical slice of behavior
  2. Run the test — confirm it fails (red)
  3. Write the minimum code to make it pass (green)
  4. Repeat from step 1 for the next slice of behavior
  5. Refactor if needed while keeping tests green

Each test should target one thin vertical slice through the system. Do not write all tests upfront — write one, make it pass, then move to the next.

For frontend code: implement directly without TDD.

4. Validate

Run the feedback loops and fix any issues. Repeat until both pass cleanly.

bun run typecheck
bun run test

5. Commit

Once typecheck and tests pass, commit the work.

Keep looking

Skills are one crate of 328,083. 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.