agentsclimarketplace

Manage tooling documentation

Skill alexe-ev/product-plugins/product-ops/skills/manage-tooling-documentation

Establish or audit tooling stacks and documentation practices for product teams. Use this skill when a team's tools or documentation are creating friction or inefficiency.From its SKILL.md

Install
npx -y skills add alexe-ev/product-plugins --skill manage-tooling-documentation

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

One thing to look at

  • 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

2.2 KB, 424 tokens by cl100k_base, as published. Nobody here has run it

Manage Tooling & Documentation

Purpose

Help teams select, configure, or audit their tooling stack and documentation practices to reduce friction and improve knowledge management.

Skill type

Conceptual skill

Use this skill when

  • A team's tools are fragmented and creating knowledge silos
  • Documentation doesn't exist, is outdated, or isn't used
  • A new team needs to set up its tooling stack
  • Tool consolidation is needed to reduce overhead

Do not use this skill when

  • The goal is process design for meetings (use design-operating-cadence)
  • The goal is a technical infrastructure decision (use technical-product skills)

Required inputs

  • Current tooling landscape (even rough list)
  • Team type and size
  • Key documentation needs

Optional inputs

  • Pain points with current tools
  • Budget constraints
  • Cross-team tool dependencies

Upstream context

Works best when:

  • Team structure and operating cadence are defined
  • Key workflows are mapped

Downstream handoff

Output can feed:

  • automate-workflow-governance
  • align-cross-team-communication

Instructions

  1. Audit current tooling across: planning, documentation, communication, analytics, roadmapping.
  2. Identify redundancies, gaps, and friction points.
  3. Recommend a rationalized tooling stack.
  4. Define documentation standards: where things live, naming conventions, update cadence.
  5. Identify what should be documented but isn't.
  6. Produce a documentation health assessment.

Output

Provide:

  • Current tooling audit
  • Recommended tooling stack by category
  • Documentation standards
  • Documentation health assessment (what exists, what's missing, what's outdated)
  • Recommended actions for immediate improvement
  • Governance: who owns tool administration and documentation upkeep

Risks / caveats

  • Tool sprawl is a symptom of process problems, not the cause — fix the process first
  • Documentation that isn't used is waste — design for findability and maintenance
  • Avoid recommending major tooling changes without understanding migration cost

What ships with it: 4 files

7.0 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,537. 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.