Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yogsoth-ai/forced-connection
Force connection between two unrelated concepts. Deliberately construct bridging paths where no natural connection exists.
Passed 5 of 21 test cases with the skill, and 4 of 21 without it.
1 fixed4 passed either way18 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I noticed that when performing forced connection exercises between distant concepts, a dedicated subagent is recommended rather than running it directly in the primary context. What specific creative challenge does a subagent overcome in forced connection tasks?
| Checked | Without skill | With skill |
|---|---|---|
| The answer states that forced connections require sustained creative pressure to resist declaring no connection exists. | Missed | Passed |
| The answer states that dedicated context prevents declaring early that no connection can be found. | Missed | Passed |
The instructions your model reads when the skill loads.
Force connection between two unrelated concepts.
Subagent — spawned via subagent-spawning/spawn-agent skill.
Forced connection requires sustained creative pressure — the subagent must resist declaring "no connection exists" and instead push through discomfort to find bridging paths. Benefits from dedicated context that commits fully to the bridging process.
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent. |
test cases passed, vs 4 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.