Break down goals into multiple tasks and coordinate execution with gates and recovery. Based on Claw Code's agentic harness.
92
90%
Does it follow best practices?
Impact
100%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
This guide walks you through claiming and promoting the planning-execution-harness skill on Tessl.
npm install -g tessl
tessl --versioncd ~/planning-execution-harness
tessl skill import . --workspace <your-workspace>This updates tile.json with Tessl metadata.
tessl skill lint .
tessl skill review --optimize .Both commands should pass without critical errors.
TESSL_TOKENPush to main and GitHub Actions automatically publishes:
cd ~/planning-execution-harness
git add .github/workflows/tessl-publish.yml
git commit -m "Add Tessl publishing workflow"
git push origin mainCheck Actions tab in GitHub to see the workflow run.
cd ~/planning-execution-harness
export TESSL_TOKEN="your-token-here"
tessl skill publish . --token $TESSL_TOKENAfter publishing, verify your skill is live:
To update the published skill:
SKILL.md, schemas, or examplestile.json:
{
"version": "1.0.1"
}Once published, promote it:
Wait 2-3 minutes for indexing, then refresh https://tessl.io/registry.
TESSL_TOKEN secret is set in GitHub SettingsCheck:
SKILL.md frontmatter is valid YAMLname, descriptionUse linter:
tessl skill lint .Check:
.github/workflows/.yml extensionSKILL.mdtile.jsonexamples/schemas/contracts/If Tessl auto-indexed your repo before you formally published:
This ensures you're listed as owner in the registry.
Your optimized tile.json will look like:
{
"name": "benpiper-workspace/planning-execution-harness",
"version": "0.2.0",
"private": false,
"summary": "Use when you need to architect a multi-language, language-agnostic system...",
"skills": {
"planning-execution-harness": {
"path": "SKILL.md"
}
}
}Key fields (auto-optimized by Tessl):
name — Workspace-qualified identifier (tessl adds your workspace)version — SemVer (auto-updated on publish)summary — From SKILL.md frontmatter descriptionprivate — false to publish publiclyskills — Path to SKILL.md fileYour SKILL.md should start with:
---
name: planning-execution-harness
description: Use when you need to architect a multi-language system that separates high-level planning from low-level execution with gating, recovery, and permission control.
---Critical for discovery:
description must include "Use when..." for agent activationgit add .github/workflows/tessl-publish.yml
git commit -m "Add Tessl publishing workflow"
git push origin mainYour skill is ready to share with the world! 🚀