Sponsor Finder
github/awesome-copilot
Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors.
This skill should be used when someone needs to find, propose, or evaluate a focal point in a coordination, negotiation, or alignment problem.
$ npx skills add gnurio/nurijanian-skills --skill focal-point-finder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gnurio/nurijanian-skills focal-point-finder --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/gnurio/nurijanian-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/focal-point-finder .claude/skills/focal-point-finder && 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 "focal-point-finder" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/focal-point-finder into .claude/skills/focal-point-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focal-point-finder", 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/gnurio/nurijanian-skills/tree/main/skills/focal-point-finderType 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 gnurio/nurijanian-skills --skill focal-point-finder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gnurio/nurijanian-skills focal-point-finder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/focal-point-finder .agents/skills/focal-point-finder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "focal-point-finder" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/focal-point-finder into .agents/skills/focal-point-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focal-point-finder", 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 gnurio/nurijanian-skills --skill focal-point-finder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gnurio/nurijanian-skills focal-point-finder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/focal-point-finder .cursor/skills/focal-point-finder && 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 "focal-point-finder" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/focal-point-finder into .cursor/skills/focal-point-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focal-point-finder", 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/gnurio/nurijanian-skills.git --path skills/focal-point-finder--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 gnurio/nurijanian-skills --skill focal-point-finder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gnurio/nurijanian-skills focal-point-finder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/focal-point-finder .gemini/skills/focal-point-finder && 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 "focal-point-finder" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/focal-point-finder into .gemini/skills/focal-point-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focal-point-finder", 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 gnurio/nurijanian-skills focal-point-finderInstalls 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 gnurio/nurijanian-skills --skill focal-point-finder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/focal-point-finder .github/skills/focal-point-finder && 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 "focal-point-finder" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/focal-point-finder into .github/skills/focal-point-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focal-point-finder", 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 gnurio/nurijanian-skills --skill focal-point-finder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gnurio/nurijanian-skills focal-point-finder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/focal-point-finder .opencode/skills/focal-point-finder && 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 "focal-point-finder" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/focal-point-finder into .opencode/skills/focal-point-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focal-point-finder", 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.
focal-point-finderThis skill should be used when someone needs to find, propose, or evaluate a focal point in a coordination, negotiation, or alignment problem.
Focal Point Finder is an agent skill from gnurio/nurijanian-skills. This skill should be used when someone needs to find, propose, or evaluate a focal point in a coordination, negotiation, or alignment problem. A focal point is a solution that people converge on without explicit agreement — because it is uniquely prominent, simple, or recognizable. Based on Thomas Schelling's "The Strategy of Conflict." Triggers on "where should we align?", "how do we get everyone on the same page?", "what's the obvious choice?", "find a focal point", "Schelling point", "coordination problem"…
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/schelling-focal-points.md`).
The repository describes itself as: Claude Code and Cursor skills for product managers — PM coaching, verbalized sampling, tech sensemaking, and more. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 43a0566. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Focal Point Finder loads about 3.2k tokens when it runs, and up to ~5k if it reads all its reference files. Until then it costs about 186 tokens; SKILL.md has 1,684 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.
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.
The full file from gnurio/nurijanian-skills at commit 43a0566, republished under its MIT licence (© gnurio). 1,684 words, ~3,223 tokens.
.claude/skills/focal-point-finder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Identify, evaluate, or create focal points in coordination and negotiation problems using Thomas Schelling's framework from The Strategy of Conflict.
A focal point is not the objectively best outcome. It is the outcome that everyone expects everyone else to expect — the one choice that stands out enough for mutual recognition. The authority is in the expectations themselves, not in the thing expectations attach to.
Extract the structure of the situation by answering:
Present the map to the user for validation before proceeding.
Before proposing anything new, identify what focal points already exist. Check each source:
Uniqueness — Is there one option that stands alone, qualitatively different from all others? Test: "If not this, what?" — if there is no clear alternative, it is focal.
Example: On a map with many crossroads but one house, all 11 people who picked the house met. The 4 who picked crossroads each chose a different one and none met. Three houses would have destroyed the focal point — uniqueness avoids ambiguity.
Simplicity — Is there a clean, discrete option vs. many that differ only by degree? Test: "Can this be stated in one sentence without qualifiers?"
Example: Poison gas was not used in WWII despite no formal treaty. "No gas" is binary and unambiguous. "Some gas" (how much? where? against whom?) creates impossible coordination. The simplicity of total abstention made it the only tacitly achievable limit.
Precedent — Has this been done before in a similar situation? Is there a pattern everyone knows? Test: "What happened last time?"
Example: Middle Eastern oil royalties converged on the 50-50 formula within years of the first deal setting that pattern. Subsequent negotiations had "no heart left in the bargaining" under the shadow of that precedent.
Symmetry — Is there a mathematically or aesthetically balanced option (50-50, equal, round numbers)? Test: "Does this feel 'fair' by default?"
Example: Two strangers secretly divide $100 into piles A and B. If splits match, both keep $100. 36 out of 40 chose $50/$50 — not because it is fair, but because it is the only split both can be certain the other will also pick.
Cultural Salience — Is there something that this specific group of people would all recognize as obvious? Test: "Would a newcomer to this group guess the same answer?"
Example: "Meet somewhere in NYC, no instructions." Most chose Grand Central Station, information booth, 12 noon. The answer depends entirely on the people — a sample from Tokyo would converge elsewhere.
For each candidate focal point found, rate its strength:
If a strong focal point already exists, present it and stop. The user's job is to recognize it, not to invent a new one.
If there is no existing focal point or the obvious one is being ignored, diagnose why:
| Symptom | Likely Cause | Schelling Remedy |
|---|---|---|
| Too many options, no one commits | No option has qualitative uniqueness | Strip away options until one stands alone |
| Everyone has a different "obvious" answer | Cultural salience differs across parties | Find common ground — shared precedent, shared reference points |
| The obvious answer is unfair to one party | The focal point discriminates | Accept it if miscoordination is worse, or find an equally prominent alternative |
| Someone introduced conflicting data | Noise is drowning the signal | Simplify: remove extraneous variables |
| The old default was breached | Precedent was broken without a replacement | Establish a new bright line quickly, before the vacuum fills with chaos |
| Agreement in principle, but endless debate on degree | Trying to compromise on a continuum | Find a qualitative boundary (river, not "some miles") |
When no natural focal point exists, create one using these techniques (ordered by reliability).
Key principle: finding a focal point requires imagination, not just logic. Schelling notes that "poets may do better than logicians at this game, which is perhaps more like 'puns and anagrams' than like chess." Accidental arrangements, humor, and even whimsy can become focal if they are the only things that stand out.
Make a visible, specific proposal before anyone else does. Even a mediocre proposal gains power from being the only proposal.
"The strongest argument in favor of R is the rhetorical question, 'If not R, what then?'"
Requirements for this to work:
Recruit someone respected by all parties to make a "dramatic suggestion." The suggestion fills the vacuum of indeterminacy.
The mediator's power comes not from the quality of the suggestion but from the fact that it exists. A traffic cop at a jammed intersection helps even the drivers most disadvantaged by the routing.
Reformulate the situation to make a favorable outcome appear as the "obvious" choice:
If the existing focal point is unfavorable, flood the situation with additional variables until the old signal is drowned out and parties retreat to a simpler default (often 50-50).
Replace "how much?" questions with "which category?" questions. Continuous variables have no focal point. Discrete categories do.
In strategic conflict, actions authenticate intentions more than words. Incur a visible cost or risk to make a proposal credible. A team that migrates its codebase to a new framework before the "standards meeting" has created a focal point through action, not argument.
An option that is not even available can still magnetize expectations. The "shadow" of a 50-50 split coordinates expectations even when the rules make an exact 50-50 impossible. When proposing a focal point, reference a familiar benchmark even if it cannot be achieved exactly — it pulls the final answer toward it.
Before presenting the proposed focal point, verify it passes these tests:
Before presenting a recommendation, verify it does not fall into these traps:
Optimizing instead of coordinating. The recommendation proposes the "best" answer instead of the most recognizable one. A territory split along the most equitable population line is objectively better than the river — but nobody can independently identify the same equitable line. The river wins because both sides can find it without talking.
Bad: "Divide the region by population density, giving each side roughly equal citizens." Good: "The river. It is the only line both sides will independently draw."
Proposing quantitative limits on a continuum. The recommendation suggests a specific number or percentage when a qualitative boundary exists. Nuance kills coordination — any number can slide to the next number.
Bad: "Limit chemical weapons to 50kg per engagement with monitoring provisions." Good: "No chemical weapons. Binary, unambiguous, no negotiation needed."
Offering multiple options. The recommendation presents 3 "equally good" alternatives and asks the user to choose. The entire purpose of a focal point is singularity — one answer that commands attention by having no competitor. Presenting options is the opposite of finding a focal point.
Bad: "Here are three viable pricing models: per-seat, per-action, or flat monthly." Good: "Per-seat monthly. It has the most precedent from adjacent SaaS. The others may be better, but this is the one everyone will independently guess."
Ignoring discrimination. The recommendation rejects a focal point because it is "unfair" to one party, when the cost of miscoordination is worse than the unfairness. Schelling: "beggars cannot be choosers about the source of their signal." A discriminatory focal point that coordinates is often better than a fair proposal that nobody can independently identify.
Bad: "The river disadvantages the eastern population, so we should find a more equitable line." Good: "The river disadvantages the east, but the 15 people who tried to draw a 'fairer' line produced 14 different answers. The river is the only line that works."
Structure the output as:
## Focal Point Analysis
**Situation**: [One-sentence description of the coordination problem]
**Parties**: [Who must align]
**Stakes of Miscoordination**: [What happens if they fail to converge]
### Existing Focal Points
[List any found in Step 2 with strength ratings]
### Diagnosis
[If convergence is failing, why — from Step 3]
### Recommended Focal Point
[The specific proposal]
**Why this works**:
- [Which magnets it activates: uniqueness, simplicity, precedent, symmetry, cultural salience]
- [Why alternatives are weaker]
**How to establish it**:
- [Which technique from Step 4: be first, mediator, framing, noise, qualitative boundary]
- [Specific actions to take]
**Risks**:
- [What could undermine it]
- [What happens if it is breached]
**Stress Test Results**:
- If Not Here, Where? → [pass/fail]
- Newcomer Test → [pass/fail]
- Breach Test → [pass/fail]
- Concession Test → [pass/fail]
- Stability Test → [pass/fail]For detailed source quotes, examples, and the full Schelling methodology, read references/schelling-focal-points.md.
© gnurio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in skills/focal-point-finder of gnurio/nurijanian-skills.
Open the folder on GitHubat commit 43a0566
Focal Point Finder 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 |
|---|---|---|---|---|---|---|
| Focal Point Finder this skillgnurio/nurijanian-skills | 124 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Sponsor Findergithub/awesome-copilot | 40k | 1 repos | ~3k | Automated safety check: Pass | MIT | |
| Flutter PR Checks Finderflutter/flutter | 180k | — | ~1.3k | Automated safety check: Pass | BSD-3-Clause | |
| Smart Contract Entry Point Analyzertrailofbits/skills | 7.5k | 1 repos | ~2.4k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Extension PointsBuilderIO/agent-native | 7.1k | — | ~2.4k | Automated safety check: Pass | None | |
| Extension Pointsdotnet/skills | 5.6k | 1 repos | ~2.9k | Automated safety check: Pass | MIT |
github/awesome-copilot
Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors.
flutter/flutter
Find failing checks on a Flutter PR and locate the corresponding LUCI log URLs.
trailofbits/skills
Maps the state-changing entry points of a smart contract codebase and sorts them by access level, producing a structured audit report that leaves out read-only functions.
BuilderIO/agent-native
How extensions render as widgets inside other apps via named UI slots — the framework's optional extension system.
dotnet/skills
Own MSBuild import and hook discovery. An agent skill from dotnet/skills.
brycewang-stanford/Auto-Empirical-Research-Skills
Find and assess datasets for a research question. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.
gnurio/nurijanian-skills
This skill should be used when a user wants to identify which parts of a codebase are safe to modify with AI ("vibe code") and which require careful human engineering.
gnurio/nurijanian-skills
Find, diagnose, and fix misalignment in corporate settings. An agent skill from gnurio/nurijanian-skills.
gnurio/nurijanian-skills
Generate diverse outputs by prompting for a probability distribution instead of a single response.
gnurio/nurijanian-skills
PM alignment coach and router. An agent skill from gnurio/nurijanian-skills.
gnurio/nurijanian-skills
Analyze technology announcements to surface non-obvious strategic implications using Verbalized Sampling.
gnurio/nurijanian-skills
PM stress-test roleplay. An agent skill from gnurio/nurijanian-skills.
This skill should be used when someone needs to find, propose, or evaluate a focal point in a coordination, negotiation, or alignment problem. Focal Point Finder is an agent skill from gnurio/nurijanian-skills. This skill should be used when someone needs to find, propose, or evaluate a focal point in a coordination, negotiation, or alignment problem.
Focal Point Finder fits situations like: where should we align?; how do we get everyone on the same page?; whats the obvious choice?; find a focal point.
Run `npx skills add gnurio/nurijanian-skills --skill focal-point-finder -a claude-code`. Or copy the skill folder (skills/focal-point-finder in gnurio/nurijanian-skills) into .claude/skills/focal-point-finder in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gnurio/nurijanian-skills --skill focal-point-finder -a codex`. Or copy the skill folder (skills/focal-point-finder in gnurio/nurijanian-skills) into .agents/skills/focal-point-finder in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gnurio/nurijanian-skills --skill focal-point-finder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/focal-point-finder, .gemini/skills/focal-point-finder, .github/skills/focal-point-finder and .opencode/skills/focal-point-finder in your project.
SKILL.md names no scripts, command-line tools or credentials: Focal Point Finder is instructions for the agent only.
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.
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.
Focal Point Finder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Focal Point Finder: Sponsor Finder (github/awesome-copilot, 40k stars), Flutter PR Checks Finder (flutter/flutter, 180k stars), Smart Contract Entry Point Analyzer (trailofbits/skills, 7.5k stars) and Extension Points (BuilderIO/agent-native, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
gnurio (a GitHub user) maintains it in gnurio/nurijanian-skills, which has 124 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on August 13, 2026.
Source: gnurio/nurijanian-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.