Name: propstack
Rating: 56.8 (1 reviews)
Author: membranedev

propstack

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

Quality

65%

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

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 content is well-structured and actionable with strong connection-workflow guidance, but it lacks validation/verification steps for the destructive-capable action and proxy operations, and the "Popular actions" section underdelivers versus its heading.

Suggestions

Add a validation/verification step after running actions or proxy requests (e.g. inspect the `output`/response status, confirm the expected record changed, retry on error) to lift workflow_clarity past the destructive-ops cap.

Populate "Popular actions" with actual commonly-used Propstack actions (e.g. list properties, create contact, update deal) with example commands instead of repeating the discovery command.

Move the proxy flag reference table and the connection state-machine detail into a separate reference file (e.g. REFERENCE.md) and link to it one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and brief notes, with only minor padding (e.g. "so you can focus on the integration logic rather than auth plumbing") and a discovery command repeated under "Popular actions".	4 / 5
Actionability	It provides many concrete, executable commands (login, connection ensure, action list/run, request) plus a thorough flag table, but "Popular actions" only repeats discovery instead of listing actual popular actions and examples rely on placeholders.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with explicit state checkpoints and retry polling, but the skill performs destructive-capable operations (arbitrary action runs, proxy DELETE) with no output validation or verification steps, triggering the destructive-ops cap of 3.	3 / 5
Progressive Disclosure	It is a single well-organized file with clear section headers and no external references, but at over 50 lines the inlined flag table and connection state-machine details could be split into separate reference files.	4 / 5
	Total	15 / 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 answers both what and when and is anchored to a distinct brand, but its action language is generic and its trigger terms lack the synonyms and concrete nouns (CRM, real estate, leads, deals) that would make it sharply match user intent.

Suggestions

Replace generic verbs with concrete Propstack actions, e.g. "Manage leads, properties, deals, and marketing campaigns".

Expand the trigger clause with natural user phrases: "Use when the user wants to manage Propstack CRM records, properties, deals, or contacts."

Mention the commercial real estate / CRM niche so the skill triggers distinctly from general data tools.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Propstack domain and a couple of action categories, but the verbs are generic and coverage is not comprehensive, matching the anchor that names domain plus 1-2 actions.	3 / 5
Completeness	Both a "what" (manage data/records, automate workflows) and a "when" ("Use when the user wants to interact with Propstack data") are present, though the when clause is generic rather than listing concrete triggers.	4 / 5
Trigger Term Quality	The description includes relevant keywords ("Propstack", "data", "interact with Propstack data") but misses common variations and synonyms a user might say (CRM, real estate, leads, deals, properties).	3 / 5
Distinctiveness Conflict Risk	"Propstack" is a distinct brand niche with minimal conflict risk, but the generic "manage data" and "automate workflows" phrasing leaves minor overlap with other data-management skills.	4 / 5
	Total	14 / 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/propstack/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.