Individual skill

type-relation

0upvotes

Classify relations among entities using an explicit relation ontology and state evidence/assumptions for the type.

skills/type-relation/SKILL.md

Read pinned source

Source commit 41f752b8444ed9030dd9dc223c302ce874e51f83

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 511
Repository last updated: Oct 23, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

academic-research Repository topic
deep-research Repository topic
literature-review Repository topic
mcp Repository topic
skill Repository topic
ai-scientist Repository topic
auto-research Repository topic
claude-code Repository topic
research-agent Repository topic
scientific-discovery Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,677 bytes

Read excerpt


# type-relation
## Purpose
Classify relations among entities with an explicit relation ontology and evidence for the chosen type.
## Input contract
```yaml
required: [entity_pair, relation_ontology, evidence_register]
optional: [candidate_relation_types, scope_ledger, prior_edges]
constraints: [relation type, direction, scope, and evidence are explicit]
```
## Procedure
1. Verify that both entities are in scope and normalize their identifiers.
2. Enumerate candidate relation types and test each against its defining conditions.
3. Select the best-supported type or record ambiguity, then state direction and evidence.
4. Emit the typed relation, rejected types, and follow-up evidence needed to resolve uncertainty.