agentsclimarketplace
Sign in

Stakeholder comms

Skill hartmut-ux/ai-marketing-team/skills/stakeholder-comms/.claude/skills/stakeholder-comms

Creates stakeholder communications including investor updates, board reports, annual impact reports, and partner communications aligned with B Corp PSG standards. Use when user asks about investor relations, board communications, stakeholder reporting, impact reports, annual reports, or partner/supplier communications.From its SKILL.md

Install
npx -y skills add hartmut-ux/ai-marketing-team --skill stakeholder-comms

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

  • 11 stars11 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.0 KB, 180 tokens by cl100k_base, as published. Nobody here has run it

Stakeholder Comms — Claude Code wrapper

This is the Claude Code wrapper for stakeholder-comms. The full skill definition lives in shared/SKILL-CORE.md in the same skill folder.

When to use

Use when the user asks for:

  • stakeholder-comms
  • "run stakeholder-comms"
  • Any trigger described in the core skill

How to invoke

In Claude Code:

stakeholder-comms

Instructions

  1. Read shared/SKILL-CORE.md for the platform-agnostic workflow, rules, and examples.
  2. Execute the workflow using Claude Code tools.
  3. Load any referenced files from shared/ or subdirectories relative to this skill folder.

References

  • shared/SKILL-CORE.md — full skill definition

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most operations skills give in 180 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • read the core skill definition file
  • execute the workflow using claude code tools
  • load referenced files from shared directories

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.