Name: placetel
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

placetel

Placetel integration. Manage Organizations. Use when the user wants to interact with Placetel data.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/placetel/SKILL.md

Quality

Content

56%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 body delivers executable Membrane CLI commands with a decently sequenced connection/action workflow, but it is undermined by a large padded feature list and no use of separate reference files. Inlining bulk material keeps structure mediocre.

Suggestions

Remove or drastically trim the 'Placetel Overview' bullet list; many entries (Forum, Blog Post, GDPR Compliance, Help Center) are not Placetel features and waste tokens.

Move the proxy flag reference table and full action-discovery details into a separate reference file linked from SKILL.md to improve progressive disclosure.

Add a validation step after running actions or proxy requests (e.g., inspect the `output` field / HTTP status) to close the workflow's feedback loop for potentially destructive API calls.

Dimension	Reasoning	Score
Conciseness	The ~85-item 'Placetel Overview' bullet list (Call, User, ... Forum, Blog Post, Bug Report, Feature Request) is heavy padding, much of it not Placetel-specific, and the intro explains basic product facts Claude could infer; this matches 'noticeably verbose; several unnecessary explanations or padded sections'.	2 / 5
Actionability	Concrete, runnable commands are provided throughout (npm install, membrane login, connection ensure, action list/run, request) with flag tables, fitting 'mostly executable guidance with minor gaps' such as the unresolved CONNECTION_ID placeholder.	4 / 5
Workflow Clarity	The connect-wait-search-run sequence is clearly laid out with state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, matching 'clear sequence with most checkpoints present; minor validation gaps' like no output verification after running an action.	4 / 5
Progressive Disclosure	No bundle files exist and all content (the large feature enumeration plus the proxy flag table) is inlined in one 234-line file, fitting 'some structure but could be better organized; content that should be separate is inline.'	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 correctly states both what the skill does and when to use it, with third-person voice and a distinct product name. Its weakness is narrow specificity and a generic trigger clause lacking natural synonyms.

Suggestions

Expand the 'what' clause to list 2-3 concrete Placetel capabilities (e.g., manage calls, users, voicemail, call routing) instead of only 'Manage Organizations'.

Make the trigger more natural and specific, e.g., 'Use when the user wants to query, create, or update Placetel calls, users, voicemail, or call-routing settings.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Placetel) and one concrete action ('Manage Organizations'), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it does not enumerate the breadth of Placetel capabilities.	3 / 5
Completeness	Both 'what' ('Placetel integration. Manage Organizations.') and 'when' ('Use when the user wants to interact with Placetel data.') are present, but the trigger clause is generic and could be more specific.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Placetel data' surfaces the 'Placetel' keyword but offers no synonyms or common phrasings users would naturally say, fitting 'some relevant keywords but missing common variations.'	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Placetel' gives it a clear niche with low conflict risk, but the otherwise generic phrasing leaves minor overlap with other CRM/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/placetel/SKILL.md
Commit: f484c82

Reviewed: 5 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.