CtrlK
BlogDocsLog inGet started
Tessl Logo

planning-center

Planning Center integration. Manage Persons, Groups, Lists, Events, Medias. Use when the user wants to interact with Planning Center data.

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/planning-center/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 is highly actionable with executable commands throughout and a solid connection-state workflow, but it is held back by unnecessary background prose and missing validation/verification for destructive action and proxy calls.

Suggestions

Add a verification checkpoint after running actions or proxy mutating requests (e.g., re-fetch the resource or check the response status/error field) so destructive operations have an explicit validate step.

Label the post-connection steps explicitly (define "Step 2") or remove the dangling "skip to Step 2" reference so the sequence is unambiguous.

Trim the background paragraph about what Planning Center is and who uses it, plus editorializing like "so you can focus on the integration logic rather than auth plumbing," to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient command reference, but the opening "Planning Center is a suite... used by church administrators, pastors, and ministry leaders" and "so you can focus on the integration logic rather than auth plumbing" add background and editorializing Claude does not need.

3 / 5

Actionability

Copy-paste-ready commands cover install, auth, connect, search, run, and proxy, with a complete flags table and clearly marked placeholders, fully covering the common cases.

5 / 5

Workflow Clarity

The connection setup has explicit state checks and poll/re-poll loops, but "skip to Step 2" references an unlabeled step and mutating proxy/action calls (POST/PUT/PATCH/DELETE) lack result verification, so the destructive-operation cap applies.

3 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no nested references provides good navigation; with no bundle files present there are no buried or multi-level references to penalize.

4 / 5

Total

15

/

20

Passed

Description

78%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 cleanly answers both what the skill does and when to use it with concrete entity names and third-person voice. Its main limitation is a single generic trigger phrase and a single generic action verb, which keep it just short of the top anchors.

DimensionReasoningScore

Specificity

"Manage Persons, Groups, Lists, Events, Medias" names five concrete entity types, but the single verb "Manage" is generic rather than enumerating distinct actions, so it sits below the comprehensive 5 anchor.

4 / 5

Completeness

Both "what" ("Manage Persons, Groups, Lists, Events, Medias") and "when" ("Use when the user wants to interact with Planning Center data") are explicit, but the "when" is a single generic phrase rather than multiple concrete triggers, fitting the 4 anchor.

4 / 5

Trigger Term Quality

"Planning Center" plus the entity names (Persons, Groups, Events) give good natural keyword coverage, but the trigger clause offers only one phrase and omits common variations or scenarios, leaving it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Planning Center" is a specific proper-noun church-management application with distinct triggers, giving a clear niche and minimal conflict risk.

5 / 5

Total

17

/

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.