Name: cincopa
Rating: 60.8 (1 reviews)
Author: membranedev

cincopa

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

Quality

71%

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

Quality

Content

76%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 highly actionable, copy-paste-ready CLI guidance with a well-structured connection workflow and clear sections. Its main weakness is the absence of validation or confirmation steps for the destructive delete operations, which caps workflow clarity.

Suggestions

Add an explicit validation/confirmation step before destructive actions, e.g. 'Confirm the asset/gallery ID with the user before running delete-asset or delete-gallery, and verify the deletion with a follow-up list call.'

Tighten padding in the auth and best-practices prose (e.g. drop 'so you can focus on the integration logic rather than auth plumbing') to push conciseness toward 5.

Consider moving the 20-row popular-actions table into a references file (e.g. ACTIONS.md) and linking to it, keeping SKILL.md as a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and a tight one-line platform intro, but contains minor padding such as 'so you can focus on the integration logic rather than auth plumbing', fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the lean level 5 or the noticeably verbose level 3.	4 / 5
Actionability	Commands like 'membrane connection ensure', 'membrane action list --intent "QUERY"', and 'membrane action run <actionId> --input' are copy-paste ready and the popular-actions table covers common cases, matching the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling, but destructive actions (delete-asset, delete-gallery, delete-live-stream, delete-webhook) appear with no validation or confirmation guidance, triggering the rubric cap that holds workflow clarity at 3.	3 / 5
Progressive Disclosure	The single-file skill is well organized into clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices), but the 20-row action table is inline and the skill exceeds the under-50-line simple-skill exception, fitting the 'good structure; minor organization gaps' anchor rather than the ideal one-level-deep reference level 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 the skill does and when to use it with a clearly distinct named platform, but its action language is generic and its trigger phrasing lacks natural synonyms. It is solid but could be sharpened with more concrete Cincopa-specific operations.

Suggestions

Replace generic verbs with concrete Cincopa actions, e.g. 'Manage videos, galleries, live streams, and webhooks; upload assets and update metadata.'

Add natural trigger variations users would say, e.g. 'Use when the user wants to manage Cincopa videos, galleries, or live streams.'

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Cincopa domain with a couple of actions, but those actions are generic rather than concrete platform-specific operations, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the fully concrete level 5 or the minimal level 2.	3 / 5
Completeness	Both 'what' ('Cincopa integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Cincopa data') are present and explicit, but the trigger could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than the level-5 concrete-trigger example.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Cincopa data' surfaces the platform keyword but offers no synonyms or natural variations, matching the 'some relevant keywords but missing common variations' anchor rather than the comprehensive level 5.	3 / 5
Distinctiveness Conflict Risk	The named platform 'Cincopa' creates a clear niche with distinct triggers and minimal conflict risk against other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 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/cincopa/SKILL.md
Commit: f484c82

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