cross-ecosystem-synergy-detection SKILL.md skillA
cross-ecosystem-synergy-detection from chrono-meta/forge-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrono-meta/forge-harness/cross-ecosystem-synergy-detection@git:20261031.27f6430Pins git:20261031.27f6430 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrono-meta/forge-harness
- Path
plugins/fh-meta/skills/cross-ecosystem-synergy-detection/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261031.27f6430, committed Oct 31, 2026
- First version recorded
- Jun 3, 2026
- Size
- 23,094 bytes
- Repository stars
- 31
- License
- MIT
Automatically discovers useful combinations (synergy pairs) across multiple installed plugins and skills, and presents them as a ranked table. Proactively suggests undiscovered synergies when new projects or skills are registered in the registry. Activates on phrases like "do my installed tools work well together?", "they seem to work in isolation", "find synergies".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# cross-ecosystem-synergy-detection — Multi-Ecosystem Automatic Synergy Discovery Automatically discovers cross-invocable pairs in environments with multiple installed plugins and cross-CLI tools, and derives a synergy ranking table. ## Activation Triggers 1. **Multi-ecosystem component environment specified**: "multiple plugins/cross-CLI installed", "synergy with other components", "cross-ecosystem", "run together" 2. **New component added/removed**: "component install", "add/remove component" 3. **Synergy check phrasing**: "are they working in isolation?", "can they be integrated?", "environment check", "combination effect" 4. **Registry change detected** (optional): If a user-maintained `LOCAL_SKILL_REGISTRY.md` is present, Step 7 runs when a new project/skill is registered. The registry is not auto-created — absent file → Step 7 reports `[NOT-CONFIGURED]` and skips its body (see Step 7-1 outcome table). **Exception**: Single-component environments (1 or fewer installed → no meaningful activation) ### Natural Language Triggers (General user phrasing — activates without internal vocabulary) | Example phrasing | Intent | |---|---| …
Read the whole file at its exact version.
How to install
mdr add chrono-meta/forge-harness/cross-ecosystem-synergy-detection@sha256:dfc0f09e467bd090The line at the top of this page pins the label git:20261031.27f6430, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3sbaqjzudrd7xaar)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 3, 2026 and Oct 31, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.27f6430 latest | 2026-10-31 | 27f6430 | 23,094 B | A | view · diff |
| git:20260823.9f674da | 2026-08-23 | 9f674da | 24,016 B | A | view · diff |
| git:20260822.e06c499 | 2026-08-22 | e06c499 | 22,583 B | A | view · diff |
| git:20260822.b750491 | 2026-08-22 | b750491 | 16,347 B | A | view · diff |
| git:20260811.eede7ad | 2026-08-11 | eede7ad | 13,251 B | A | view · diff |
| git:20260603.4031ba1 | 2026-06-03 | 4031ba1 | 8,812 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (23094 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chrono-meta/forge-harness · 31 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3sbaqjzudrd7xaar GET https://markdownregistry.com/api/v1/resolve?ref=chrono-meta/forge-harness/cross-ecosystem-synergy-detection GET https://markdownregistry.com/api/v1/blob/dfc0f09e467bd0909dd8fd17fc8201f5dc598d4db30d96160b3f730d518ae716
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.