Name: timecamp
Rating: 52.8 (1 reviews)
Author: membranedev

timecamp

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

Quality

59%

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

Quality

Content

56%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 solid, executable Membrane CLI instructions with a well-handled connection-readiness workflow, but it is undercut by a large padded feature list and lacks result validation or progressive file structure. Trimming the overview and adding verification guidance would materially raise quality.

Suggestions

Delete or collapse the ~57-item "TimeCamp Overview" bullet list (Login, Sign Up, Pricing, Blog, etc.) — it is padding that competes for context without adding actionable guidance.

Add a validation/verification step after running actions (e.g. check the `output`/`error` fields and retry on non-READY states), especially since actions can perform writes.

Move the detailed feature inventory and proxy flag reference into a separate reference file and link to it, keeping SKILL.md a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The ~57-item bullet list under "TimeCamp Overview" (Login, Sign Up, Pricing, Free Trial, Blog, GDPR, etc.) is substantial padding that adds no actionable value, matching the anchor for noticeably verbose content with padded sections; the surrounding CLI guidance is efficient but the list drags the whole down.	2 / 5
Actionability	Commands are concrete and copy-paste ready (`membrane connection ensure`, `membrane action run`, `membrane request`) with a flag table for proxy options, but they rely on placeholders like CONNECTION_ID and actionId and omit a fully worked end-to-end example, so it stops just short of fully executable coverage.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run sequence, and the connection-readiness polling with explicit READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR branches is a real feedback loop, but there is no validation checkpoint on action results, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Sections are reasonably organized, but the large inlined feature/concept list is content that should be trimmed or moved out, and the only external pointer is a bare docs URL with no internal reference structure, fitting the anchor for some structure with content that should be separate kept inline.	3 / 5
	Total	13 / 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 correctly uses third person and answers both what and when with an explicit "Use when" trigger, but its action language is generic boilerplate rather than concrete TimeCamp-specific capabilities. It is competent but undifferentiated from sibling integration skills.

Suggestions

Replace generic verbs with concrete TimeCamp actions, e.g. "Track time entries, manage projects and tasks, pull timesheet and attendance reports, and approve time off."

Expand the trigger to mention natural user phrasings like time tracking, timesheets, billable hours, or project hours rather than only "TimeCamp data".

Add a file-format or entity cue (e.g. time entries, timesheets, reports) so the trigger is less likely to collide with other Membrane integration skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("TimeCamp integration") plus a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, matching the anchor for naming a domain with 1-2 actions that aren't comprehensive.	3 / 5
Completeness	Both halves are present — a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with TimeCamp data"), but the "what" is generic so it does not reach the concrete-trigger level of 5.	4 / 5
Trigger Term Quality	The natural trigger is essentially just "TimeCamp" (repeated as "TimeCamp data"), with no synonyms or varied phrasings, fitting the anchor for some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	"TimeCamp" names a specific SaaS product giving it a clear niche and low conflict risk, but the generic boilerplate verbs (manage data, records, automate workflows) are shared across similar Membrane integration skills, leaving minor overlap risk.	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/timecamp/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.