Name: papyrs
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

papyrs

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

Quality

62%

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

Quality

Content

67%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 a solid, actionable integration guide with concrete commands and a well-sequenced, validated connection workflow. Its main weakness is mild verbosity and structural redundancy between action-discovery sections.

Suggestions

Collapse the "Popular actions" section into "Searching for actions" to remove the near-duplicate `membrane action list` guidance.

Fix the step numbering so the "Step 2" reference resolves (label the connection step "1" before "1b. Wait for the connection to be ready").

Trim the introductory "Papyrs is a web-based intranet..." sentence and the agent-types aside, or move them to a reference file, to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and focused on Membrane specifics Claude would not know, but it includes some over-explanation ("Papyrs is a web-based intranet and knowledge management system...", the agent-types aside) and redundant overlap between the "Searching for actions" and "Popular actions" sections.	3 / 5
Actionability	It provides concrete, copy-paste-ready bash commands for install, login, connection, action list/run, and proxy (with a full flag table); the minor gap is the absence of a Papyrs-specific worked example showing a real action id and its output.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced (ensure -> wait -> inspect state) with an explicit feedback loop (poll again after CLIENT_ACTION_REQUIRED) and error handling for CONFIGURATION_ERROR/SETUP_FAILED; minor gaps come from the dangling "Step 2" reference and the "1b" heading without a labeled "1a/Step 1".	4 / 5
Progressive Disclosure	No bundle files exist, so everything lives in one well-organized SKILL.md with clear section headers; at ~140 lines with some content (the proxy flag table, connection state machine) that could be split out, it is good but not the lean simple-skill case that would score 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 identifies a specific niche (Papyrs) and includes an explicit trigger, but it is vague about concrete capabilities and relies on generic phrasing rather than the natural terms users would say. Specificity and trigger-term coverage are the main weaknesses.

Suggestions

Replace the generic "Manage Organizations" with the concrete actions the skill supports, e.g. "Search, create, and comment on Papyrs pages; manage users and forms".

Broaden the trigger clause with natural synonyms a user might say, e.g. "Use when the user wants to work with their Papyrs intranet, wiki, pages, forms, or search Papyrs content".

Keep the explicit "Use when..." trigger but tie it to specific data types (pages, comments, attachments) rather than the abstract "interact with Papyrs data".

Dimension	Reasoning	Score
Specificity	It names the domain ("Papyrs integration") and a single minimal/generic action ("Manage Organizations"), with the remainder being generic ("interact with Papyrs data"); it does not list the concrete capabilities the body actually exposes (pages, forms, users, search).	2 / 5
Completeness	Both a "what" ("Papyrs integration. Manage Organizations.") and an explicit "Use when..." trigger are present; the "when" could be more specific about which interactions, matching anchor 4 rather than anchor 3 (which requires the when to be missing/weakly implied).	4 / 5
Trigger Term Quality	It surfaces the relevant natural keyword "Papyrs" ("Use when the user wants to interact with Papyrs data"), but misses common variations and synonyms a user might say such as intranet, wiki, pages, forms, or search.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Papyrs gives it a clear niche with low conflict risk, but the generic phrasings ("Manage Organizations", "interact with Papyrs data") leave minor overlap risk with broad org/data-management skills.	4 / 5
	Total	13 / 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/papyrs/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.