Name: superoffice
Rating: 59.2 (1 reviews)
Author: membranedev

superoffice

SuperOffice integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with SuperOffice data.

Quality

68%

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

Quality

Content

63%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 operational core is excellent — executable commands, a clear connection state machine, and good action discovery guidance. The skill is dragged down by a huge padded term list that hurts conciseness and would be better split into a reference file or deleted.

Suggestions

Remove or move the ~160-line 'SuperOffice Overview' bullet list into a separate reference file; it duplicates terms (Delete, Merge, Import, Export, etc.) and adds no actionable guidance.

Define the referenced 'Step 2' with an actual heading so the connection workflow's skip targets are unambiguous.

Add a brief validation/verification note for destructive proxy calls (e.g. 'membrane request ... -X DELETE') since the proxy permits arbitrary destructive HTTP methods.

Dimension	Reasoning	Score
Conciseness	The 'SuperOffice Overview' is a ~160-line bullet list of nouns/verbs (with duplicates such as Delete, Merge, Import, Export, Print, Send, Receive) ending in 'Use action names and parameters as needed' — a large padded section that does not teach Claude anything actionable.	2 / 5
Actionability	Concrete copy-paste commands throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action list/run', 'membrane request'), a proxy flags table, and a popular-actions table of real action keys cover the common cases.	5 / 5
Workflow Clarity	A clear connect→search→run sequence with a state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback loops; 'Step 2' is referenced but never defined as a heading, a minor gap.	4 / 5
Progressive Disclosure	There are no bundle files and section headers organize the operational content, but the 160-line entity/action enumeration is inline content that belongs in a separate reference file (or should be removed).	3 / 5
	Total	14 / 20 Passed

Description

73%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 solid, on-brand description that answers both what and when and is highly distinct. Its main weakness is reliance on one generic verb ('Manage') and a tautological trigger clause rather than richer action and trigger language.

Suggestions

Replace the generic 'Manage' with two or three concrete verbs (e.g. 'Create, update, and list Persons, Organizations, Deals, Leads, Projects') to lift specificity.

Expand the 'Use when' clause with concrete triggers users actually say, e.g. 'Use when the user wants to manage SuperOffice CRM data — contacts, sales/deals, tickets, or projects'.

Add common synonyms ('CRM', 'tickets', 'sales') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names many concrete entities ('Persons, Organizations, Deals, Leads, Projects, Activities') but relies on a single generic action verb ('Manage ... and more'), so the actions described are minimal rather than comprehensive.	3 / 5
Completeness	Both 'what' ('Manage Persons, Organizations, Deals...') and 'when' ('Use when the user wants to interact with SuperOffice data') are present and explicit, but the when-clause is somewhat tautological and could name concrete triggers.	4 / 5
Trigger Term Quality	'SuperOffice' plus natural CRM entity terms (Deals, Leads, Projects) give good keyword coverage, though common synonyms like 'CRM', 'tickets', and 'sales' are missing.	4 / 5
Distinctiveness Conflict Risk	'SuperOffice' is a specific named CRM with a clear niche and entity-specific triggers, giving minimal overlap with other skills.	5 / 5
	Total	16 / 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/superoffice/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.