Name: companycam
Rating: 48.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

companycam

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

Quality

53%

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

Quality

Content

46%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 actionable Membrane CLI guidance is strong and executable, but the body is crippled by a massive inlined list of irrelevant entities that destroys token efficiency and structure. Destructive actions also lack validation checkpoints.

Suggestions

Delete the entire 'CompanyCam Overview' entity list (lines 21-897); it is almost entirely unrelated to CompanyCam and wastes ~85% of the file's tokens.

If a real entity/data-model overview is needed, keep only CompanyCam-relevant entities (User, Company, Group, Project, Photo, Document, Tag) and move detail to a references file.

Add a validation/confirmation step before destructive actions (delete-project, delete-photo, archive-project), e.g. 'Confirm the project ID with the user before running delete-project'.

Dimension	Reasoning	Score
Conciseness	The 'CompanyCam Overview' is a ~870-line dump of entity names, the overwhelming majority irrelevant to CompanyCam (Greek gods, planets, stars, hundreds of 'Kepler-NNNb' exoplanets, foundations, legal concepts), making the body severely verbose and heavily padded. Not a 2 because the padding is extreme and pervasive, not just several unnecessary explanations.	1 / 5
Actionability	The working sections provide fully executable, copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request proxy) plus a concrete Popular actions table covering common cases. Not below 5 because the common cases are specifically covered with real commands.	5 / 5
Workflow Clarity	The connection flow is sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop, but destructive/batch actions (delete-project, delete-photo, archive-project) are listed with no validation or confirmation checkpoints. Per the rubric cap, missing validation for destructive operations caps this at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the file is monolithic; the giant inlined overview list is content that clearly should be removed or split out rather than placed inline in SKILL.md. Not a 3 because the inlined noise dominates the structure rather than being an isolated organizational gap.	2 / 5
	Total	11 / 20 Passed

Description

61%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 correctly answers both 'what' and 'when' in third person and targets a distinct niche, but it is thin on concrete capabilities and natural trigger keywords. Strengthening the action list and trigger terms would lift specificity and trigger quality.

Suggestions

Replace 'Manage Organizations' with concrete actions, e.g. 'List and create projects, upload and tag photos, manage users and tags'.

Expand the 'Use when' clause with natural triggers: 'when the user mentions CompanyCam, jobsite photos, project photos, or wants to manage CompanyCam projects, photos, tags, or users'.

Add concrete trigger nouns/synonyms (photos, projects, tags, jobsite documentation) to improve natural keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("CompanyCam integration") and a single generic action ("Manage Organizations"), but lists no concrete, specific operations. Not a 3 because it does not enumerate 1-2 concrete actions like 'list projects' or 'upload photos'.	2 / 5
Completeness	It states both what ("CompanyCam integration. Manage Organizations.") and when ("Use when the user wants to interact with CompanyCam data."), but the 'when' clause is generic and could name concrete triggers. Not a 5 because the trigger phrases are not concrete and multi-faceted.	4 / 5
Trigger Term Quality	"CompanyCam" is a natural term users would say, and "interact with CompanyCam data" provides a relevant phrase, but synonyms, variations, and concrete trigger contexts (e.g. 'photos', 'jobsite', 'projects') are missing. Not a 4 because keyword coverage is thin rather than merely missing a few natural terms.	3 / 5
Distinctiveness Conflict Risk	"CompanyCam" is a specific branded niche with distinct triggers, so the risk of activating for the wrong skill is minimal. Clear niche with distinct triggers as the anchor describes.	5 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1045 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/companycam/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.