# Techtide Cross Harness Export Hygiene > Prepare skills and agents for cross-harness export by separating canonical SKILL.md assets from Cursor rules, Kiro steering, and prompt-kit adapters. Use when an agent needs Alex Cinovoj / TechTide live-coding patterns, tool routing, guarded prototype-to-production workflows, or cross-harness prompt/skill adapters. Use when this capability is needed. - Skill: `tomevault-io/techtide-cross-harness-export-hygiene` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/techtide-cross-harness-export-hygiene` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/techtide-cross-harness-export-hygiene/raw - Safety review: pending (external: skill-scanner PASS, skillspector CAUTION) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/techtide-cross-harness-export-hygiene --- # TechTide Cross Harness Export Hygiene Prepare skills and agents for cross-harness export by separating canonical SKILL.md assets from Cursor rules, Kiro steering, and prompt-kit adapters. ## Source Pattern This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load `references/source-patterns.md` when you need the source anchors and extraction rationale. Load `references/adapter-map.md` when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs. ## Workflow 1. Start from the canonical skill and identify which harnesses have a compatible skill primitive. 2. Strip or transform frontmatter only for harnesses with stricter schemas. 3. Use notices, rules, steering, or prompt kits where a platform lacks SKILL.md support. 4. Run exporter coverage and bundling tests after catalog changes. 5. Document lossy adapter behavior honestly. ## Output Contract Return a concise brief with these fields: - harness matrix - adapter notes - export validation - catalog update - verification performed or still required - security and privacy notes ## Guardrails - Extract reusable methods, not private local content. - Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports. - Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values. - Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions. - Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts. ## Harness Policy - Use this as a native `SKILL.md` for Claude Code, Codex, Gemini, and Copilot-compatible exports. - For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule. - For Kiro, create steering only when the workflow can be made short and inclusion-scoped. - For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts. --- > Source: [TechTideOhio/techtide-harness-kit](https://github.com/TechTideOhio/techtide-harness-kit) — distributed by [TomeVault](https://tomevault.io).