telos

Read or safely update personal TELOS, or analyze project documentation for goals, dependencies, bottlenecks, narratives, reports, and dashboards. Use for life goals, beliefs, strategies, TELOS updates, project relationship analysis, narrative points, or professional TELOS reports. Do not use for general constitutional interviews.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./Skills/product-strategy/telos/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, safety-conscious runbook with concrete validation commands and clear sequencing. Its main weakness is that the referenced workflow and tool files are absent from the bundle, weakening both actionability and progressive disclosure.

Suggestions

Ship the referenced Workflows/Update.md, InterviewExtraction.md, CreateNarrativePoints.md, and WriteReport.md (and Tools/UpdateTelos.ts) in the bundle so the signaled navigation actually resolves.

Consolidate the repeated backup/changelog/partial-failure guidance into one section to tighten conciseness.

Inline a minimal executable snippet or step list for the core personal-update write so the primary action does not depend solely on missing workflow files.

Dimension	Reasoning	Score
Conciseness	Dense, assumes Claude's competence, and avoids explaining what TELOS is; minor repetition of the backup/changelog/partial-failure guardrail across the Personal TELOS contract, Failure mode, and Gotchas sections keeps it just below a 5.	4 / 5
Actionability	Provides concrete executable commands ("python3 -m unittest -v ...", "./bin/ask skills audit ...", "./bin/ask skills resolve telos --json --robot") and names specific tools (Tools/UpdateTelos.ts, TOOLS/LifeosConfig.ts); the core update procedure is delegated to workflow files that are not present in the bundle, a minor gap.	4 / 5
Workflow Clarity	The personal-update contract is a clear numbered sequence with validation checkpoints (validate, backup, stop without writing on failure) and an explicit failure-mode feedback loop; held at 4 because the detailed per-workflow steps live in referenced files not present here.	4 / 5
Progressive Disclosure	Sections are well-organized and the four Workflows/*.md references are well-signaled and one level deep, but none of the referenced workflow or tool files exist in the bundle, so the intended split is not actually navigable.	3 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete actions, explicit trigger phrases, and a clear negative boundary that distinguishes it from the related interview skill. Minor room to add a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("Read or safely update personal TELOS", "analyze project documentation for goals, dependencies, bottlenecks, narratives, reports, and dashboards") with only minor coverage gaps; not a full 5 because the actions lean slightly abstract.	4 / 5
Completeness	Explicitly answers both what ("Read or safely update personal TELOS, or analyze project documentation...") and when ("Use for life goals, beliefs, strategies...") with concrete trigger phrases, plus a negative boundary.	5 / 5
Trigger Term Quality	"Use for life goals, beliefs, strategies, TELOS updates, project relationship analysis, narrative points, or professional TELOS reports" gives good natural keyword coverage; a few synonyms/common variations are missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	The niche term TELOS and the explicit "Do not use for general constitutional interviews" disambiguation give a clear niche with minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Skills/product-strategy/telos/SKILL.md
Commit: f1f2f21

Reviewed: ~4 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.