skill-neuroanalytics-data-science-harness-people · by Install
$ agentstack add skill-neuroanalytics-data-science-harness-people ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-neuroanalytics-data-science-harness-people) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill: people
Maintain the project's people as structured Metadata: each contributor with their CRediT roles and persistent identifiers, so credit is explicit, standard-coded, and machine-readable — and so it flows into the dataset's Authors and, at release, DataCite creators. The canonical record is the ledger contributors[]; you delegate the save to the datalad doer.
CRediT roles (use these exact terms): Conceptualization, Data curation, Formal analysis, Funding acquisition, Investigation, Methodology, Project administration, Resources, Software, Supervision, Validation, Visualization, Writing – original draft, Writing – review & editing.
When to use
- The user wants to add/update a contributor, assign CRediT roles, or record ORCIDs/affiliations.
- Do NOT use to write a report (
project/status-report) or to mint DOIs (disseminate/dataset-release).
Steps
- Capture the contributor —
name,orcid(as an ORCID URL, if known),affiliation_ror
(ROR URL, if known), and their roles from the CRediT list above. Ask; do not guess an ORCID or invent roles.
- Upsert into
contributors[](perdocs/project-ledger.md) — match byname(or ORCID) and
update, or add a new entry. Keep roles to valid CRediT terms; do not duplicate a person.
- Reflect into
dataset_description.json— update theAuthorslist to match (order is the
author order the team agrees on). Keep it consistent with the ledger.
- Log it — append
{ ts, op: people, stage: manage, note: "credited ()", branch: }. - Save — delegate to the datalad doer: "save:
datalad save -m 'people: credit '." - Report — the updated contributor list with roles, and any missing ORCIDs/affiliations to fill.
Constraints
- Use only valid CRediT role terms (listed above); never invent a role or an ORCID/ROR — record only
identifiers the user provides.
- Keep
contributors[]de-duplicated (one entry per person) and consistent with
dataset_description.json Authors.
- Upsert per the ledger conventions; keep
log:append-only and the ledger schema-valid. Delegate
the save to the datalad doer.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: neuroanalytics
- Source: neuroanalytics/data-science-harness
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.