apply-deploy-to-strength

apply-deploy-to-strength is a skill for Claude Code from jeffreytse/grimoire-core. It costs 65 tokens per session (3,920 once invoked), scanned A, original, MIT.

A method for assigning people to important roles by matching the exact abilities a role needs with the abilities each candidate actually has.

In plain words
What is it for?
Use it to staff projects, select technical or operational leads, and compare candidates against role-specific requirements.
Why use it?
It avoids treating general excellence or seniority as proof that someone fits a particular job, reducing the risk of putting the wrong person in a critical role.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 145 skills shipped together

Good fit Use it to staff projects, select technical or operational leads, and compare candidates against role-specific requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/apply-deploy-to-strength
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jeffreytse/grimoire-core --skill apply-deploy-to-strength
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 145 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for apply-deploy-to-strength

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-deploy-to-strength/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-deploy-to-strength)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-deploy-to-strength"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-deploy-to-strength/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for apply-deploy-to-strength

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-deploy-to-strength"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-deploy-to-strength.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,920 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.03920
Opus 5 $0.00032 $0.01960
Sonnet 5 $0.00013 $0.00784
Haiku 4.5 $0.00006 $0.00392

Measured 9d ago against content hash 781a6d96a4d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

apply-deploy-to-strength scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/business/strategy/skills/apply-deploy-to-strength/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Apply Deploy to Strength

Before assigning someone to a high-stakes role, map the specific capability profile the role actually requires — not a generic "strong performer" template — and match it against what each candidate specifically has; a gap in the role-critical requirement is a match failure regardless of the candidate's overall excellence, and deploying excellence-as-proxy for role-specific fit produces failure.

Why This Is Best Practice

Origin: Zhuge Liang's 将苑 (Way of the General, ~220–234 AD) devotes Chapter 13 "智用" (Intelligent Use) to the principle of deploying people according to their specific capabilities, not their general status. The key passage: "智者取其谋,愚者取其力,勇者取其威,怯者取其慎。" (From the wise, take their strategy; from the strong, take their force; from the brave, take their authority; from the cautious, take their care.) The principle is not that the wise should only do strategy and should never be deployed elsewhere — it is that each person has a specific dimension of excellence that constitutes their deployable contribution to a specific type of operation. The great commander knows which dimension each person possesses and assigns operations to exploit that dimension, rather than assigning the person who is highest-ranked or most trusted overall.

The evidence in practice: Zhuge Liang assigned Zhao Yun (veteran, defensive specialist, renowned for composed operations under pressure) to holding and screening operations — roles that required exactly Zhao Yun's specific profile. He assigned more aggressive young generals to offensive thrusts that required their specific profiles. The campaigns that followed the 将苑 doctrine succeeded operationally. The campaign that did not — the Battle of Jieting (228 AD) — failed because Zhuge Liang assigned Ma Su to a role that required battlefield command experience specifically. Ma Su was among the most gifted strategic analysts in Shu Han; Zhuge Liang's personal affection for him was genuine; his overall talent was exceptional. But the Jieting assignment required the specific capability of battlefield unit command under pressure — which Ma Su had never done — not strategic analysis, which was Ma Su's actual strength. Zhuge Liang himself acknowledged the error: his grief at Ma Su's execution was not only personal, but acknowledged that his own matching failure had created the situation.

Read the full file on GitHub · 128 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 128 lines · 65 tokens per session scan A 781a6d96a4d4

Subscribe to this mod's changes

apply-deploy-to-strength is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 24d ago), licensed MIT. It adds 65 tokens to every session and 3,920 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.