linked-data
Skill3 starsChanged 8 months agoCC0-1.0View on GitHub
Applies Tim Berners-Lee's linked data principles (four rules, dereferencing, browsable graphs, FOAF/seeAlso, 5-star linked open data). Use when designing or reviewing RDF publishing, HTTP URIs for things, 303 redirects, SPARQL endpoints, semantic web data linking, or explaining LOD and open data star ratings.
In this repository48 other files it gives its agents.
- 3d-printingSkill
- app-securitySkill
- architecture-designSkill
- aws-genai-lensSkill
- aws-well-architected-frameworkSkill
- aws-well-architectedSkill
- azure-well-architectedSkill
- blog-post-with-diagramsSkill
- clean-architectureSkill
- clean-codeSkill
- databricks-genie-spaces-best-practicesSkill
- data-visualization-guideSkill
- design-an-interfaceSkill
- design-patternsSkill
- domain-driven-designSkill
- dry-principleSkill
- edit-articleSkill
- event-driven-designSkill
- git-best-practicesSkill
- git-guardrails-claude-codeSkill
- grill-meSkill
- hexagonal-architectureSkill
- improve-codebase-architectureSkill
- language-conventions-source-en-docs-brSkill
- learn-electronicsSkill
- microservices-skillSkill
- object-oriented-programmingSkill
- oop-design-patternsSkill
- oreilly-design-referenceSkill
- organize-docs-from-zipSkill
- prd-to-issuesSkill
- prd-to-planSkill
- project-context-syncSkill
- request-refactor-planSkill
- rfc2119Skill
- scaffold-exercisesSkill
- semverSkill
- setup-pre-commitSkill
- solid-principlesSkill
- tddSkill
- todoSkill
- triage-issueSkill
- ts-otp-awsSkill
- ubiquitous-languageSkill
- ux-design-principlesSkill
- write-a-prdSkill
- write-a-skillSkill
- yagni-principleSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use this skill when the task touches RDF on the web, cool URIs, dereferencing, linking datasets, or open-data publishing - not for generic …
- Very specific: line 26
Use relative links inside this repo to LinkedDataDesignIssues.md.
- Very specific: line 30
Add explicit fragment IDs in Markdown headings elsewhere (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Linked data
When to apply
Use this skill when the task touches RDF on the web, cool URIs, dereferencing, linking datasets, or open-data publishing - not for generic REST APIs unless the conversation is explicitly about RDF graphs and URI/HTTP lookup patterns.
MUST
- Read the canonical note in LinkedDataDesignIssues.md before giving detailed guidance; prefer its wording and structure over paraphrase when citing rules.
- Preserve the four expectations as behavioral norms (URI names, HTTP URIs, useful representations on lookup, links to other URIs) - see the note's numbered list and "four rules" section.
- Distinguish Linked Data from Linked Open Data (licence / openness) when the user asks about stars, government data, or "LOD".
SHOULD
- Point implementers at SPARQL, RDF syntax choices, and 303 where the note discusses variations (hash URIs vs slash URIs,
seeAlso, browsable graphs). - Mention trade-offs of fully browsable graphs (duplication, consistency) when relevant.
- Use relative links inside this repo to
LinkedDataDesignIssues.md; do not assume the W3C HTML snapshot path on disk.
MAY
- Add explicit fragment IDs in Markdown headings elsewhere (e.g.
{#fivestar}) when mirroring the note's anchors.
Primary reference
| Resource | Role |
| LinkedDataDesignIssues.md | Full converted Design Issues note (source: https://www.w3.org/DesignIssues/LinkedData.html) |
Quick checklist
- [ ] Confirmed the user means RDF/HTTP-linked data (not only JSON hypermedia)
- [ ] Re-read or skim LinkedDataDesignIssues.md for the section in scope
- [ ] Stated the four rules or linked to them explicitly
- [ ] Called out openness only when the question is about LOD or star ratingsDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.