Agent skill · Security

harness-core

Core harness library providing standardized self-verification, checkpoint management, drift detection, and audit logging utilities for all NeuroClaw skills. This is NOT directly called by users; instead, it is imported as a Python module by other skills for harness-compliant execution, validation, and reproducibility. Use this as a foundation/plugin SDK when building or enhancing other skills. Triggers: none (library import only). This skill provides: HarnessController class, VerificationRunner, CheckpointManager, DriftDetector, AuditLogger, DependencyManifest, and related utilities.

BioTender-maxgithub.com/BioTender-maxGitHub ↗
claude-codeships scriptsNOASSERTION
Install
npx skills add BioTender-max/awesome-bio-agent-skills --skill harness-core --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: yes
Requires: []
Path: skills/neuroclaw/harness-core/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 135
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Harness Core Library ## Overview `harness-core` is the **base SDK / plugin library** for implementing NeuroClaw harness engineering standards across all skills. Instead of reimplementing validation, checkpointing, logging, and drift detection in every skill, `harness-core` provides reusable, well-tested Python classes and utilities that all other skills can import and extend. **Key design principle**: Harness-awareness is **not optional** — every data-processing, model-execution, and experiment-running skill should import from this library to achieve: - Standardized self-verification across all skills - Reproducible, hash-verified experiment logs - Automatic checkpoint/resume capability - Drift detection and anomaly alerts - Privacy-preserving audit trails ### When to Use This Skill **Directly**: Rarely — this is a library, not a user-facing skill. **Indirectly (as a dependency)**: - When developing or modifying skills like `experiment-controller`, `run_models`, `fmri-skill`, `smri-skill`, etc. - When using skills that have been enhanced to support harness engineering - When integrating external tools or models into NeuroClaw (inherit harness patterns) ## Core Components ### 1. H

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Core Components
  4. 1. HarnessController (Main Orchestrator)
  5. 2. VerificationRunner
  6. 3. CheckpointManager
  7. 4. DriftDetector
  8. 5. AuditLogger
  9. 6. DependencyManifest
  10. Python API Reference
  11. HarnessController
  12. VerificationRunner
  13. DriftDetector
  14. AuditLogger
Ships with 1 file
  • __init__.py
More from awesome-bio-agent-skills
All skills →
About this skill
What does the harness-core skill do?

Core harness library providing standardized self-verification, checkpoint management, drift detection, and audit logging utilities for all NeuroClaw skills. This is NOT directly called by users; instead, it is imported as a Python module by other skills for harness-compliant execution, validation, and reproducibility. Use this as a foundation/plugin SDK when building or enhancing other skills. Triggers: none (library import only). This skill provides: HarnessController class, VerificationRunner, CheckpointManager, DriftDetector, AuditLogger, DependencyManifest, and related utilities.

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill harness-core --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going