Name: talkspirit
Rating: 53.6 (1 reviews)
Author: membranedev

talkspirit

TalkSpirit integration. Manage data, records, and automate workflows. Use when the user wants to interact with TalkSpirit data.

Quality

60%

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/talkspirit/SKILL.md

Quality

Content

57%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.

The content is actionable with concrete commands and a well-handled connection state machine, but it is padded with background prose, has a broken 'Step 2' cross-reference with no post-action validation, and inlines reference material that should be split out.

Suggestions

Trim the opening overview paragraph and editorializing asides; Claude does not need TalkSpirit's market positioning to use the CLI.

Fix the dangling 'skip to Step 2' reference by either labeling steps explicitly or removing the forward reference, and add a verification step after running actions or proxy requests (e.g. check the `output`/status field before proceeding).

Move the clientAction schema breakdown and proxy flags table into a separate reference file and link to it, and either populate 'Popular actions' with concrete examples or remove the empty heading.

Dimension	Reasoning	Score
Conciseness	The bulk is lean command reference, but the opening overview ('Think of it as a company-wide social network...') and editorializing asides ('so you can focus on the integration logic rather than auth plumbing') are unnecessary explanation Claude doesn't need.	3 / 5
Actionability	Provides copy-paste-ready commands for the full workflow (install, login, connection ensure, action list/run, request) plus a flags table, with only minor gaps such as the abstract proxy endpoint '/path/to/endpoint' and a generic input example.	4 / 5
Workflow Clarity	The connection-readiness flow has explicit state branching and a polling feedback loop, but the body references a 'Step 2' that is never defined, and there is no validation of action/proxy results before proceeding.	3 / 5
Progressive Disclosure	Reasonable section structure, but it is a single ~158-line file with no bundle references, inlining material that could live separately (clientAction schema details, the proxy flags table), and the 'Popular actions' heading contains no actual popular actions.	3 / 5
	Total	13 / 20 Passed

Description

62%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.

The description covers both what and when with a distinct brand trigger, but the stated capabilities are generic ('data, records, workflows') rather than concrete TalkSpirit actions, and trigger-term coverage is narrow.

Suggestions

Replace generic verbs with concrete TalkSpirit actions, e.g. 'Post messages, manage channels and groups, create events and articles, and automate workflows'.

Broaden the 'Use when...' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to send or read TalkSpirit messages, manage channels/groups, or automate TalkSpirit workflows'.

Mention recognizable TalkSpirit nouns (channels, messages, events, tasks) to improve trigger-term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (TalkSpirit) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete TalkSpirit-specific operations (post message, create channel, etc.).	3 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with TalkSpirit data'), though the trigger phrasing is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes the natural brand term 'TalkSpirit' and the phrase 'interact with TalkSpirit data', but lacks common variations or synonyms (messages, channels, posts, teams) that users would say.	3 / 5
Distinctiveness Conflict Risk	The named brand 'TalkSpirit' gives it a clear niche with low conflict risk, but the generic 'data/records/workflows' phrasing overlaps with other SaaS-integration skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/talkspirit/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.