CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/tessl-publish-public

Ensure Tessl tiles meet all requirements for public registry publishing with comprehensive validation, quality gates, and evaluation scenarios. Use when preparing skills for public Tessl release, validating tile.json configuration, creating evaluation scenarios, enforcing quality thresholds, or checking agent-agnostic compliance. Keywords: tessl, tile, publishing, public-registry, validation, quality-gates, tile.json, evaluation-scenarios, skill-publishing

94

Quality

94%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

scenario-08.mdevaluation-scenarios/

Scenario 08: Edge Case - Missing tile.json

User Prompt

"Publish the new custom-logging skill publicly to Tessl."

Expected Behavior

  1. Agent locates skill directory at skills/observability/custom-logging/
  2. Agent checks for tile.json file existence
  3. Agent discovers tile.json is missing
  4. Agent recognizes this is a new skill without Tessl import yet
  5. Agent suggests running tessl skill import skills/observability/custom-logging first
  6. Agent explains import creates tile.json with proper structure
  7. Agent blocks publication until tile.json exists and is configured
  8. Agent provides step-by-step guidance for import → configure → publish workflow

Success Criteria

  • Agent checks for tile.json existence
  • Agent identifies missing tile.json as blocker
  • Agent suggests tessl skill import command
  • Agent explains import process and purpose
  • Agent does NOT attempt publication without tile.json
  • Agent provides complete workflow for new skill publishing
  • Agent mentions configuring private: false after import
  • Agent sets proper expectations for multi-step process

Failure Conditions

  • Agent attempts tessl skill publish without tile.json
  • Agent doesn't check for tile.json existence
  • Agent manually creates tile.json instead of using import
  • Agent skips import step entirely
  • Agent doesn't explain why import is necessary
  • Agent provides incomplete workflow guidance
  • Agent doesn't mention private: false configuration requirement

evaluation-scenarios

scenario-01.md

scenario-02.md

scenario-03.md

scenario-04.md

scenario-05.md

scenario-06.md

scenario-07.md

scenario-08.md

scenario-09.md

SKILL.md

tile.json