techtide-harness-kit
CLAUDE.md0 starsChanged 6 months agoApache-2.0View on GitHub
This repository is a curated marketplace for cloud, zero-trust, and compliance-aware AI workflows. - Keep changes scoped and traceable to the task. - Update catalog metadata when adding, moving, or removing cataloged assets. - Run npm run validate before finishing. The pipeline runs seven gates: validate:catalog, validate:aws, manifest:check, validate:allowed-tools, validate:skill-schema, validate:agent-schema, validate:links. Markdownlint and codespell run separately as the Docs Quality workflow (advisory npm run lint:docs). - If skills/** changed intentionally, also refresh catalog/skill-manifest.json with npm run manifest:write. - Every…
In this repository10 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- catalog/AGENTS.mdAGENTS.md
- mcp/AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- schemas/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
The file
We split this CLAUDE.md into the rules it gives an agent
12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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
- could be automatic: a setting could enforce it
- Distinctive: line 17
Prefer official docs and live evidence over memory.
- Distinctive: line 18
Default to least privilege, zero trust, and safe rollback paths.
- Distinctive: line 20
Treat broad permissions, destructive automation, and MCP mutation paths as high risk.
- Distinctive: line 21
Do not add secrets, credentials, tokens, tenant IDs, or customer data.
- Distinctive: line 25
Keep changes scoped and traceable to the task.
- Distinctive: line 26
Update catalog metadata when adding, moving, or removing cataloged assets.
- Very specific: line 27
Run npm run validate before finishing.
- Very specific: line 32
If skills/ changed intentionally, also refresh catalog/skill-manifest.json with npm run manifest:write.
- Very specific: line 34
Every SKILL.md must declare an allowed-tools field (least-privilege baseline) and conform to schemas/skill.frontmatter.schema.json.
- Distinctive: line 45
Keep portable logic in canonical specs and shared docs.
- Distinctive: line 46
Keep harness-specific behavior in the right adapter format.
- Distinctive: line 47
Do not invent unsupported metadata fields in executable agent files.
≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md 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
TechTide Harness Kit
This repository is a curated marketplace for cloud, zero-trust, and compliance-aware AI workflows.
What this repo contains
skills/- reusable workflows for recurring engineering tasksagents/- expert roles with judgment for review, architecture, and operationsrules/- harness-specific operating guidancemcp/- MCP references and trust-boundary notescatalog/- machine-readable indexesschemas/- metadata contractsdocs/- governance, taxonomy, compatibility, and quality guidance
Operating stance
- Prefer official docs and live evidence over memory.
- Default to least privilege, zero trust, and safe rollback paths.
- Separate verified facts, judgment, assumptions, and unknowns.
- Treat broad permissions, destructive automation, and MCP mutation paths as high risk.
- Do not add secrets, credentials, tokens, tenant IDs, or customer data.
When working in this repo
- Keep changes scoped and traceable to the task.
- Update catalog metadata when adding, moving, or removing cataloged assets.
- Run
npm run validatebefore finishing. The pipeline runs seven gates:validate:catalog,validate:aws,manifest:check,validate:allowed-tools,validate:skill-schema,validate:agent-schema,validate:links. Markdownlint and codespell run separately as theDocs Qualityworkflow (advisorynpm run lint:docs). - If
skills/**changed intentionally, also refreshcatalog/skill-manifest.jsonwithnpm run manifest:write. - Every
SKILL.mdmust declare anallowed-toolsfield (least-privilege baseline) and conform toschemas/skill.frontmatter.schema.json. - For agents that have a 1:1 companion skill, declare it explicitly via
companion_skills: [<skill-id>]in the agent'smetadata.jsonrather than relying on the name-stripping convention.
Cross-platform asset rule
This repo supports multiple harnesses without pretending they are identical.
- Keep portable logic in canonical specs and shared docs.
- Keep harness-specific behavior in the right adapter format.
- Do not invent unsupported metadata fields in executable agent files.
Important files
README.md- human-facing vision and repository storyAGENTS.md- compressed agent-focused repo guidanceCONTRIBUTING.md- contributor onboarding and submission pathSECURITY.md- vulnerability disclosure policy and SLACODE_OF_CONDUCT.md- community standardsdocs/compatibility.md- harness support contractdocs/normalized-platform-matrix.md- naming and platform normalizationdocs/integrations/skills-cli.md- install-path trust matrixschemas/skill.frontmatter.schema.json- required SKILL.md frontmatter contractschemas/agent.schema.json- agent metadata contract (includescompanion_skills)
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
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.

