agentleFS
PerryLinkPerryLink/dsh-research-skills/skills/data-management-plan/SKILL.md

data-management-plan

Skill0 starsChanged 5 days agoApache-2.0View on GitHub

Draft and check a data-management plan and its ethics/data-protection statements before submission.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. pedrohcgs/claude-code-my-workflow★ 1.7ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep the repository/licence/DOI fields consistent with the funder's policy.

    line 21
  2. Distinctive:

    Do not invent a repository, licence or DOI.

    line 31
  3. Distinctive:

    Do not claim ethics approval.

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data management plan

Rules

  • A DMP says where data lives, who can touch it, how long it is kept and what happens after the grant.
  • Personal data and open sharing cannot both be claimed without a lawful basis.
  • An ethics checklist pass is not ethics approval.

Steps

  1. dmp for the ten-section scaffold; fill each section with the user's facts, not boilerplate.
  2. irb for the ethics application checklist (18 starter items, risk level and safeguards).
  3. dataset_card for each dataset; run the PII-like column check before proposing open sharing.
  4. research_report the completed plan and the open questions; seal it.
  5. Keep the repository/licence/DOI fields consistent with the funder's policy.

Output

  • Completed sections with explicit unknowns.
  • Consistency findings (personal data vs open sharing, retention vs policy, backup vs repository).
  • Ethics checklist gaps and the risk level they imply.

Never

  • Do not invent a repository, licence or DOI.
  • Do not claim ethics approval.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.