CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 runbook body: clear lane separation, explicit routing to one-level-deep workflow files, a validated updater contract with backup and changelog safeguards, and exact acceptance commands. The main gaps are repetition across sections and the fact that the referenced workflow and tool files are not part of this package, leaving the core operational detail unverifiable.

Suggestions

Consolidate the repeated partial-failure/backup rules and the ReportTemplate-vs-dashboard caveats (currently restated in Workflow routing, Failure mode, Gotchas, and Expected artifacts) into a single section to tighten conciseness.

Add a minimal invocation example for Tools/UpdateTelos.ts (or fold it into Workflows/Update.md) so the personal-update lane is executable without guessing the tool's interface.

Move the long validation/acceptance command list into a referenced file (e.g. Workflows/Validation.md) or trim it to the changed-scope essentials, and ship the Workflows/ and Tools/ files referenced by the body so progressive-disclosure targets are verifiable.

DimensionReasoningScore

Conciseness

The body is a dense, directive runbook with no explanations of concepts Claude already knows ("Never hand-edit a personal TELOS file. Use `Tools/UpdateTelos.ts`, which must: 1. validate the requested file; 2. create a timestamped pre-change backup..."). It is not 5 because backup/changelog partial-failure rules and the ReportTemplate/no-dashboard caveat are each repeated across sections and the validation section runs long, and not 3 because nearly every line is actionable instruction without padding.

4 / 5

Actionability

Concrete commands and paths are given ("python3 -m unittest -v Skills/product-strategy/telos/Tools/test_update_telos.py", "./bin/ask skills audit Skills/product-strategy/telos --level compat --json --robot", "git diff --check -- Skills/product-strategy/telos") alongside explicit routing ("read [Workflows/Update.md](Workflows/Update.md)"). It is not 5 because the core update mechanics and how to invoke Tools/UpdateTelos.ts are deferred to workflow/tool files not included in this package, and not 3 because specific commands, artifacts, and acceptance criteria are spelled out.

4 / 5

Workflow Clarity

The sequence is clear with explicit validation checkpoints and feedback loops: the updater's five-step contract ("stop without writing when validation or backup creation fails"), the Failure mode section, and "After a partial failure, report whether a backup, target write, or changelog entry occurred." Destructive-write validation is present, so the workflow-clarity cap does not apply. It is not 5 because the internal sequences of each routed workflow (Update, InterviewExtraction, CreateNarrativePoints, WriteReport) are not visible in SKILL.md itself.

4 / 5

Progressive Disclosure

References are well-signaled and one level deep ("Load only the selected workflow" plus four explicit Workflows/*.md links and a See Also table). It is not 5 because none of the referenced files (Workflows/, Tools/UpdateTelos.ts, Tools/LifeosConfig.ts, ReportTemplate) ship with the package so the navigation target cannot be verified, and the inlined validation/acceptance detail is long enough that it could live in a separate file; not 3 because the structure and signaling within SKILL.md are clear.

4 / 5

Total

16

/

20

Passed

Description

83%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 that clearly separates the personal and project lanes, answers both what and when with concrete trigger phrases, and adds an explicit do-not-use boundary. Its main limits are abstract action wording and reliance on the proprietary TELOS vocabulary without synonyms or file extensions.

DimensionReasoningScore

Specificity

"Read or safely update personal TELOS, or analyze project documentation for goals, dependencies, bottlenecks, narratives, reports, and dashboards" lists several distinct actions (read, update, analyze across multiple deliverables), matching the 'several specific actions; minor gaps' anchor. It is not 5 because the actions remain abstract with no concrete operations or file formats, and not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The description explicitly answers both what ("Read or safely update personal TELOS, or analyze project documentation for goals, dependencies, bottlenecks, narratives, reports, and dashboards") and when ("Use for life goals, beliefs, strategies, TELOS updates...") with concrete trigger phrases, plus an explicit negative boundary ("Do not use for general constitutional interviews").

5 / 5

Trigger Term Quality

"Use for life goals, beliefs, strategies, TELOS updates, project relationship analysis, narrative points, or professional TELOS reports" provides good natural-phrase coverage. It is not 5 because synonyms and file extensions are absent and coverage leans on the proprietary "TELOS" term, and not 3 because several natural phrases a user would say are present.

4 / 5

Distinctiveness Conflict Risk

The TELOS niche is distinct with a clear disambiguating boundary clause, but "analyze project documentation for goals, dependencies, bottlenecks, narratives, reports, and dashboards" could still trigger on generic project-analysis or dashboard requests, leaving minor overlap risk with closely related skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.