agentsclimarketplace

Cowork

Skill alessiomarcone/agent-fieldbook/plugins/knowledge-pack/skills/cowork

Source-backed skills that turn official Claude and Codex training into reliable daily workflows.

Install
npx -y skills add alessiomarcone/agent-fieldbook --skill cowork

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

  • 17 days oldThe repository was created 17 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.
  • 3 stars3 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

Designs safe, source-grounded Cowork workflows with folders, connectors, skills, schedules, approval gates, and human verification. Use when the user asks how to delegate operational work in Cowork, automate recurring briefs, customize Cowork, or design a multi-source legal, sales, marketing, finance, or small-business workflow.

SKILL.md

2.2 KB, as published. Nobody here has run it

Cowork

Turn an operational objective into a Cowork workflow that stays reviewable and under human control.

References

  • Always read references/knowledge-base.md for product selection.
  • Read references/sources.md before making a time-sensitive product claim.
  • Read references/cowork.md and references/desktop-app.md for delegated desktop workflows.
  • Read references/claude-code-estensioni.md for Claude Code extensions.
  • Read references/plugin-building.md only for customization or distribution.

Procedure

  1. Resolve the outcome, source context, cadence, collaborators, risk, and required external systems.
  2. Confirm Cowork is the right surface: use normal Chat/Projects for conversation and shared knowledge, and Claude Code for repository engineering.
  3. Define the one-time setup: working folder, connected sources, stable instructions, and any reusable skill.
  4. Write the brief with expected output, freshness window, missing-data behavior, boundaries, and success checks.
  5. Add approval gates before messages, publishing, sensitive edits, purchases, or irreversible actions.
  6. Require source-linked verification and a human first-run review for consequential workflows.
  7. Verify current plans, UI paths, connectors, scheduling, and availability before stating them as current.

Output contract

Return:

  1. Fit — why Cowork is the right surface.
  2. Setup — folders, permissions, connectors, and reusable guidance.
  3. Ready brief — the exact on-demand or scheduled request.
  4. Approval and verification — required human gates and checks.
  5. Reuse — what should become persistent instructions, a skill, or a plugin.

Boundaries

  • Do not assume unconnected data is accessible.
  • Do not send, publish, approve, or schedule external work without authority.
  • Do not transfer Codex configuration into Claude products.
  • Answer in the user's language.

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.