CtrlK
BlogDocsLog inGet started
Tessl Logo

pingbell

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pingbell/SKILL.md
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.

The SKILL.md body is a well-structured, executable guide to driving PingBell via the Membrane CLI, with a clear connection workflow and polling checkpoints. It is slightly held back by minor fluff, placeholder parameters, and a dangling step reference.

DimensionReasoningScore

Conciseness

The body is dominated by lean, executable commands, but includes a few trimmable sentences ("This ensures minimal downtime and improved system reliability" and "so you can focus on the integration logic rather than auth plumbing"), fitting the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

It provides concrete, copy-pasteable `membrane` commands with `--json` for each phase, but relies on placeholders like CONNECTION_ID, actionId, and QUERY intent, leaving minor gaps versus fully specified examples.

4 / 5

Workflow Clarity

The install→authenticate→connect→search→run sequence is clear with polling/state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the "skip to Step 2" reference points to unlabeled steps, a minor gap.

4 / 5

Progressive Disclosure

The content is well-organized into clearly headed sections with no bundle files present and no nested references, giving good single-file structure; it stops short of a 5 only because some repeated action-list guidance could be consolidated.

4 / 5

Total

16

/

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 is functional and distinct thanks to the specific PingBell product name, with an explicit 'Use when' clause satisfying completeness. Its main weakness is thin capability coverage — only "Manage Organizations" is named — and generic trigger phrasing.

Suggestions

Expand specificity by listing 2-3 concrete PingBell actions (e.g., manage call forwarding, configure voicemail, review call history) instead of only "Manage Organizations".

Strengthen trigger terms by adding natural user phrases and synonyms such as 'incidents', 'alerts', 'on-call', or 'PingBell calls' alongside the product name.

Make the 'when' clause more concrete by tying it to specific intents (e.g., 'Use when the user wants to manage PingBell organizations, call settings, or voicemail').

DimensionReasoningScore

Specificity

The description names the domain ("PingBell integration") and one concrete action ("Manage Organizations"), but offers no other specific capabilities, matching the anchor for naming a domain plus 1-2 actions that are not comprehensive.

3 / 5

Completeness

It states both a 'what' ("PingBell integration. Manage Organizations.") and an explicit 'when' ("Use when the user wants to interact with PingBell data"), but the 'when' is generic rather than tied to concrete trigger phrases, matching the 4 anchor.

4 / 5

Trigger Term Quality

It surfaces relevant keywords ("PingBell", "Organizations", "interact with PingBell data") a user might say, but lacks common variations or synonyms beyond the product name, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"PingBell" is a specific named product giving it a clear niche with minimal conflict risk, but the generic "Manage Organizations" / "interact with data" phrasing leaves minor overlap risk with similarly-scoped integration skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.