oss-sponsors-brand-strategy skill (samber): build a company open-source sponsorship plan

• Asks up to thirteen questions one at a time until it knows mandate, budget and stack.

  Answers 4 to 6 (deadline, one-off or compounding, effort ceiling) re-rank the models and can delete the employee-nominated fund or foundation membership.

  Interview

• Picks one primary and one secondary mandate from four.

  Supply-chain assurance, reach and credibility, internal engagement, or a public values commitment. The primary breaks every later tie.

  Step 1 - Name the mandate

• Ranks four models and recommends one or two.

  Breadth, depth, foundation or consortium membership, and an employee-nominated fund. Most working programs run breadth plus one other, per SKILL.md.

  Step 2 - Choose the allocation model

• Quotes two per-developer figures labelled as published and splits the budget.

  Also lists four payment types a pledge-style program refuses to count as open-source funding.

  Step 3 - Size the budget

• Resolves your dependency tree, finds funding destinations and verifies each link.

  Uses a lockfile, an SBOM or a public dependency-resolution API when the environment can fetch URLs and read manifests; otherwise it asks for an exported dependency list.

  Network · Step 4 - Build the candidate list

• Scores candidates on four axes and sets amounts from each maintainer's ladder.

  Exposure, fragility, audience fit and relationship value. The weights are self-set and you can change them.

  Steps 5 and 6 - Rank, cut, set amounts

• Checks the payment path before any list is final.

  SKILL.md cites a $5,000 invoice minimum on the main sponsorship platform and warns that switching to invoiced billing cancels live sponsorships. It says to re-check figures before quoting.

  Step 7 - Clear procurement

• Writes a public policy and a review per mandate, with a 12-month check.

  The policy says sponsorship buys visibility, sustainability and a relationship, never roadmap position.

  Steps 8 and 9 - Policy and measurement

• Delivers a brief with nine sections, agreed one at a time.

  Mandate, Budget, Model, Targets, Amounts, Procurement, Policy, Measurement and Renewal.

  Try: “We have $80k for open source next year. Where should it go?”

  Portfolio brief

Watch out for

• It can read your dependency files and fetch URLs

  Step 4 tells the agent, when its environment allows, to resolve your dependency tree from a lockfile, SBOM or public API and to verify every funding link. Our advice: approve each lookup and use a list you are comfortable sharing. github.com

• It may keep notes in devrel-context.md

  SKILL.md tells the agent to store a few details about the current task or project, and to use a file called devrel-context.md when its memory lives in a file. Our advice: open that file before you commit or share the folder. github.com

• The plugin route installs the whole collection

  The README's plugin and extension routes add every skill in the repo; its git tree holds 93. The repo has no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Our advice: use the skills CLI command for this skill if you want only it. github.com

Security advisories