agentsclimarketplace

Core debugging strategy

Skill TechTideOhio/techtide-harness-kit/skills/core/core-debugging-strategy

Trust contracts for AI agent skills: JSON Schema risk tiers, tool permissions, deny-by-default egress, approval gates, prompt-injection fixtures, ~28 CI validation gates. Apache-2.0.

Install
npx -y skills add TechTideOhio/techtide-harness-kit --skill core-debugging-strategy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run a disciplined agent debugging loop that captures symptoms, isolates reproduction, tests hypotheses, patches narrowly, and verifies the fix. Use when expanding, reviewing, or operating skills, rules, prompt kits, provider lanes, or generated-code handoffs in the TechTide skill library.

SKILL.md

2.2 KB, as published. Nobody here has run it

Core Debugging Strategy

Run a disciplined agent debugging loop that captures symptoms, isolates reproduction, tests hypotheses, patches narrowly, and verifies the fix.

Verified Surface

  • Provider lane: core
  • Native surface: SKILL.md skill packages
  • Harness export: core
  • Import mode: techtide-synthesis
  • Source evidence: load references/source-evidence.md before promoting third-party material.

Workflow

  1. Capture the failing command, visible symptom, expected behavior, environment, and most recent change.
  2. Create the smallest reproduction before reading unrelated files.
  3. Rank hypotheses by likelihood and test them one at a time.
  4. Patch only the proven cause, then rerun the failing check and one regression-adjacent check.
  5. Record residual risk and the next guardrail to add.

Output Contract

Return:

  • provider lane and native surface
  • source evidence used
  • promotion decision or operating recommendation
  • security and privacy notes
  • verification still required

Guardrails

  • Keep third-party source bodies out of public artifacts unless direct import has clean license, attribution, and manual review.
  • Do not use star counts, popularity, screenshots, or social posts as the sole evidence for promotion.
  • Do not install or execute unreviewed external scripts as part of source research.
  • Quarantine missing licenses, unclear ownership, vague prompt packs, duplicate skill packs, and unsupported native-surface claims.
  • Preserve Alex Cinovoj / TechTide ownership for TechTide-authored synthesis while citing third-party sources as references.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.