Structured Data
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Add structured data markup.
Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships.
MITAuto-check passed
Install Strategic Alliances
$ npx skills add cbrock84/headcount --skill strategic-alliances -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount strategic-alliances --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/corporate-strategy/skills/strategic-alliances .claude/skills/strategic-alliances && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "strategic-alliances" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliances into .claude/skills/strategic-alliances/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategic-alliances", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliancesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill strategic-alliances -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount strategic-alliances --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/corporate-strategy/skills/strategic-alliances .agents/skills/strategic-alliances && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "strategic-alliances" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliances into .agents/skills/strategic-alliances/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategic-alliances", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill strategic-alliances -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount strategic-alliances --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/corporate-strategy/skills/strategic-alliances .cursor/skills/strategic-alliances && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "strategic-alliances" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliances into .cursor/skills/strategic-alliances/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategic-alliances", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/corporate-strategy/skills/strategic-alliances--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill strategic-alliances -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount strategic-alliances --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/corporate-strategy/skills/strategic-alliances .gemini/skills/strategic-alliances && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "strategic-alliances" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliances into .gemini/skills/strategic-alliances/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategic-alliances", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount strategic-alliancesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill strategic-alliances -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/corporate-strategy/skills/strategic-alliances .github/skills/strategic-alliances && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "strategic-alliances" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliances into .github/skills/strategic-alliances/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategic-alliances", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill strategic-alliances -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount strategic-alliances --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/corporate-strategy/skills/strategic-alliances .opencode/skills/strategic-alliances && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "strategic-alliances" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliances into .opencode/skills/strategic-alliances/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategic-alliances", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
strategic-alliances- GitHub stars
- 2k
- Token cost
- ~890 tokens
- SKILL.md length
- 489 words
- Files
- 1
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships.
- SKILL.md covers Partner, build, or buy, Structure by what each side…, Terms that determine whether… and Making it produce, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Strategic Alliances is an agent skill from cbrock84/headcount. Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use marketing:partnership-marketing.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
Example prompts
- “Use the strategic-alliances skill to structure partnerships that change what the business can do — technology integrations, channel and reseller…”
- “/strategic-alliances”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Strategic Alliances loads about 890 tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 489 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 489 words, ~890 tokens.
Download SKILL.mdSave it as
.claude/skills/strategic-alliances/SKILL.md (or your agent's skills folder).- name
- strategic-alliances
- description
- Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`.
Strategic alliances
Distinct from marketing partnerships. Those borrow an audience; these change what the business can do or where it can sell.
Partner, build, or buy
Partner when the capability is genuinely outside your core, the partner is materially better at it, and the arrangement can be unwound. Build when it is core, or when depending on someone else creates unacceptable exposure. Buy when you need control and speed and the thesis holds.
The question that decides it: what happens if this partner becomes a competitor, is acquired by one, or simply loses interest? If the answer is existential, do not partner — that is a build or buy decision wearing a cheaper price tag.
Structure by what each side actually wants
Partnerships fail on asymmetry of motivation more than on terms. Before structuring, establish what the partner gets, whether it is material to them, and who inside their organization is accountable for it.
A partnership that is strategically important to you and a rounding error to them will not be executed, whatever was signed. Being the small partner is workable — being the small and uninteresting partner is not.
Terms that determine whether it works
- Exclusivity — expensive, occasionally worth it, and always time-boxed. Perpetual exclusivity given away early is a recurring regret.
- Economics — who books revenue, on what split, and what happens to it if volume grows tenfold.
- Roadmap commitments — what each side will build and by when, with a remedy if they do not.
- Data — what flows where, under what basis, and what happens to it at termination.
- Customer ownership — who holds the relationship, and who may market to them afterward. Most disputed, most often left vague.
- Termination and transition — notice, and what continues for customers mid-contract. Negotiate the exit while everyone is friendly, because it will not be negotiable later.
Show full SKILL.md (188 more words)Show less
Making it produce
Signed is not launched. Partnerships need a named owner on each side, a joint plan with dates, and a regular review that either side can bring problems to.
The characteristic failure: a signed agreement, a press release, and no operational plan. Six months later both sides believe the other did not deliver, and neither is wrong.
Enable the partner properly. Their team needs to know what to say and when to bring you in, and they will not learn it from the contract.
Diagnosing a stalled partnership
Almost always one of: no accountable owner on one side, misaligned incentives at the level of the people doing the work, a promised technical dependency that never shipped, or a partner whose strategy moved.
Say it plainly and early. Partnerships die quietly for a year before anyone admits it, and that year is the cost.
Never
- Sign a partnership without naming what each side is measured on.
- Announce before the joint work has a named owner on both sides.
- Let a partnership run past its review date on goodwill.
- Grant exclusivity without a performance floor that ends it.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/corporate-strategy/skills/strategic-alliances of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Strategic Alliances next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Strategic Alliances this skillcbrock84/headcount | 2k | — | ~890 | Automated safety check: Pass | MIT | |
| Structured Datathedaviddias/Front-End-Checklist | 74k | — | ~420 | Automated safety check: Pass | MIT | |
| Bio Structural Biology Modern Structure PredictionFreedomIntelligence/OpenClaw-Medical-Skills | 3.1k | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| List Structurethedaviddias/Front-End-Checklist | 74k | — | ~438 | Automated safety check: Pass | MIT | |
| Bio Structural Biology Structure IoGPTomics/bioSkills | 1.2k | 1 repos | ~4k | Automated safety check: Pass | MIT | |
| Bio Structural Biology Structure NavigationGPTomics/bioSkills | 1.2k | 1 repos | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Bio Structural Biology Modern Structure Prediction
FreedomIntelligence/OpenClaw-Medical-Skills
Predict protein structures using modern ML models including AlphaFold3, ESMFold, Chai-1, and Boltz-1.
List Structure
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use correct list structure.
Bio Structural Biology Structure Io
GPTomics/bioSkills
Reads, writes, downloads, and converts macromolecular structures with Biopython Bio.PDB.
Bio Structural Biology Structure Navigation
GPTomics/bioSkills
Navigate the Bio.PDB SMCRA hierarchy (Structure-Model-Chain-Residue-Atom) safely, surfacing the heterogeneity it hides by default.
Bio Structural Biology Structure Preparation
GPTomics/bioSkills
Prepares a deposited or predicted structure for docking, molecular dynamics, or electrostatics by adding hydrogens, assigning protonation and tautomer states, and filling missing atoms and short…
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Questions about Strategic Alliances
What does Strategic Alliances do?
Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Strategic Alliances is an agent skill from cbrock84/headcount. Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships.
How do I install Strategic Alliances in Claude Code?
Run `npx skills add cbrock84/headcount --skill strategic-alliances -a claude-code`. Or copy the skill folder (plugins/corporate-strategy/skills/strategic-alliances in cbrock84/headcount) into .claude/skills/strategic-alliances in your project. Claude Code loads it when a task matches its description.
How do I install Strategic Alliances in Codex?
Run `npx skills add cbrock84/headcount --skill strategic-alliances -a codex`. Or copy the skill folder (plugins/corporate-strategy/skills/strategic-alliances in cbrock84/headcount) into .agents/skills/strategic-alliances in your project. Codex loads it when a task matches its description.
Can I use Strategic Alliances in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill strategic-alliances -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/strategic-alliances, .gemini/skills/strategic-alliances, .github/skills/strategic-alliances and .opencode/skills/strategic-alliances in your project.
What does Strategic Alliances need to run?
SKILL.md names no scripts, command-line tools or credentials: Strategic Alliances is instructions for the agent only.
Does Strategic Alliances access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Strategic Alliances safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Strategic Alliances use?
Strategic Alliances is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Strategic Alliances use?
About 890 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Strategic Alliances?
Skills that share tags, products or a category with Strategic Alliances: Structured Data (thedaviddias/Front-End-Checklist, 74k stars), Bio Structural Biology Modern Structure Prediction (FreedomIntelligence/OpenClaw-Medical-Skills, 3.1k stars), List Structure (thedaviddias/Front-End-Checklist, 74k stars) and Bio Structural Biology Structure Io (GPTomics/bioSkills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Strategic Alliances?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.