CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cross-disciplinary-bridge-finder

Use when identifying collaboration opportunities across fields, finding experts in complementary disciplines, translating methodologies between scientific domains, or building interdisciplinary research teams. Identifies synergies between scientific disciplines, matches researchers with complementary expertise, and facilitates cross-domain collaborations. Supports interdisciplinary grant applications and innovative research team formation.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/cross-disciplinary-bridge-finder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body suffers from heavy duplication and boilerplate, and — most seriously — its Quick Start and CLI examples reference an API and flags that the packaged script does not implement, so the main executable guidance fails as written. The workflow and error-handling sections are serviceable but generic, and most listed reference files do not exist in the bundle.

Suggestions

Rewrite the Quick Start and Command Line Usage sections against the actual script surface: e.g. `python scripts/main.py --source physics --target biology --mode bridge --output json --save matches.md`, and remove the nonexistent `scripts.interdisciplinary` / `CollaborationFinder` API (or add that module).

Deduplicate the body: collapse the two "When to Use" sections, two "References" sections, and the verbatim description pastes in "When to Use" and "Key Features", and merge the doubled Dependencies list into one consistent set of pinned versions.

Fix progressive disclosure by removing references to nonexistent files (`references/guide.md`, `references/examples/`, `references/api-docs/`) and either creating them or replacing them with the real bundle contents (e.g., `references/audit-reference.md`).

DimensionReasoningScore

Conciseness

The body is noticeably verbose and padded: the frontmatter description is pasted verbatim twice (in "When to Use" line 13, including a malformed "the task needs Use when identifying..." splice, and again in "Key Features" line 19), there are two "When to Use" sections, two "References" sections, and a Dependencies list that duplicates entries (networkx, numpy, sklearn/scikit-learn listed twice with conflicting version specs from two different requirements files). This matches the 2 anchor for several unnecessary padded sections; it is not a 1 because genuine concrete content (Quick Check commands, Handling Poor Results) is present.

2 / 5

Actionability

The headline executable examples do not run against the packaged script: the Quick Start imports `from scripts.interdisciplinary import CollaborationFinder`, but no such module or class exists in `scripts/` (main.py defines KnowledgeGraph/BridgeAnalyzer/OutputFormatter), and the CLI example uses flags (`--my-field`, `--target-field`, `--find-collaborators`, `--output matches.json`) that the actual argparse surface does not accept (`--source`, `--target`, `--mode`, `--output {json,markdown}`). The only accurate commands are the Quick Check (`python -m py_compile scripts/main.py`, `python scripts/main.py --help`), leaving minimal correct concrete guidance — a 2, not a 3, because the primary code/CLI guidance is fabricated relative to the real script rather than merely incomplete.

2 / 5

Workflow Clarity

A sequenced 5-step Workflow with a validation gate ("Validate that the request matches the documented scope and stop early"), a Quick Check before deeper execution, and a fallback/error-handling path is present — more than the bare sequence of a 2. However, the workflow is generic boilerplate never connected to the script's actual modes (bridge/complete-graph/hypothesis/landscape) or flags, and duplicated sections ("Implementation Details" pointing to "See ## Workflow above") muddy the sequence, matching the 3 anchor of steps listed with implicit or generic checkpoints rather than the 4 anchor of mode-specific validation.

3 / 5

Progressive Disclosure

The first References section points to `references/guide.md`, `references/examples/`, and `references/api-docs/`, none of which exist in the bundle; only the second References section's `references/audit-reference.md` is real. Combined with duplicated sections and a ~40KB main.py whose detail stays inlined via boilerplate rather than being split out, this matches the 2 anchor (references buried/dangling, content that should be separate kept inline); it is not a 3 because navigation actively misleads via nonexistent paths.

2 / 5

Total

9

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it explicitly answers both what the skill does and when to use it, with natural trigger phrases and good synonym coverage. Its only weaknesses are a slightly process-level verb ("facilitates") and the omission of the script's actual core capability — bridge discovery between distant fields — which would make it more accurate and distinctive.

DimensionReasoningScore

Specificity

Lists several concrete domain actions — "identifying collaboration opportunities across fields", "finding experts in complementary disciplines", "translating methodologies between scientific domains", "building interdisciplinary research teams", "identifies synergies", "matches researchers with complementary expertise", "supports interdisciplinary grant applications" — which matches the anchor for several specific actions with minor gaps. It is not a 5 because phrases like "facilitates cross-domain collaborations" are process-level rather than concrete capabilities, and the description omits the script's actual core function (discovering conceptual bridges/analogies between distant fields and generating innovation hypotheses).

4 / 5

Completeness

Both questions are explicitly answered with concrete trigger phrases: "Use when identifying collaboration opportunities across fields, finding experts in complementary disciplines, translating methodologies between scientific domains, or building interdisciplinary research teams" (when) and "Identifies synergies between scientific disciplines, matches researchers with complementary expertise, and facilitates cross-domain collaborations. Supports interdisciplinary grant applications and innovative research team formation" (what). This directly matches the 5 anchor; not a 4 because neither half is missing or only weakly implied.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: "collaboration opportunities", "experts", "interdisciplinary research teams", "grant applications", plus synonym coverage across "across fields", "cross-domain", and "interdisciplinary". A few natural terms are missing (e.g., "find collaborators", "bridge", "knowledge transfer"), which keeps it at 4 rather than 5; it is above 3 because common variations and synonyms are largely present.

4 / 5

Distinctiveness Conflict Risk

The cross-disciplinary scientific collaboration niche is mostly distinct with clear triggers ("complementary disciplines", "methodology translation", "interdisciplinary grant applications"), matching the 4 anchor. It is not a 5 because there is minor overlap risk with generic team-building, grant-writing, or literature-review skills; it is clearly above 3 since the domain framing is specific.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/cross-disciplinary-bridge-finder/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.