Name: freedcamp
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

freedcamp

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

Quality

73%

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

Quality

Content

81%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 highly actionable with executable commands and a well-validated connection workflow, which are its main strengths. The main weaknesses are mild intro/overview padding and a monolithic single-file structure that could split reference material into one-level-deep files.

Suggestions

Trim the introductory paragraph and the full Freedcamp entity hierarchy to the subset Claude actually needs to act on, reducing token cost.

Move the 'Popular actions' table and the proxy flag reference into separate reference files (e.g., ACTIONS.md) linked from the overview to improve progressive disclosure.

Optionally tighten the 'Best practices' bullets to directives only, removing restated justification that Claude can infer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the intro paragraph ("Freedcamp is a project management and collaboration tool, similar to Asana or Trello...") and the full entity hierarchy dump are mild padding Claude does not strictly need. Matches 'mostly efficient but includes some unnecessary explanation'; not a 4 because the overview padding is noticeable rather than minor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests, plus a parameter-passing example and a flags table — covering the common cases. Matches the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection setup is a clear sequenced flow with explicit validation checkpoints (state = READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a feedback loop (poll again after the user completes the action). Matches 'clear sequence with explicit validation steps; feedback loops for error recovery'.	5 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested references. It scores 4 rather than 5 because everything is inlined in one ~150-line file — the 'Popular actions' table and proxy-flag reference could live in separate one-level-deep files to slim the overview.	4 / 5
	Total	17 / 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 correctly identifies a distinct product niche and includes a 'Use when' clause, but it is thin on concrete capabilities (only 'Manage Organizations') and on natural trigger terms. Expanding both the action list and the trigger phrases would lift specificity and completeness.

Suggestions

List several concrete capabilities beyond 'Manage Organizations' (e.g., create/list tasks and projects, manage issues, track time) to raise specificity toward a 5.

Add natural trigger phrases users would actually say, e.g., 'Use when the user wants to manage Freedcamp projects, tasks, issues, or time tracking'.

Mirror the product vocabulary (projects, tasks, task lists, issues) so trigger-term coverage matches how users refer to Freedcamp data.

Dimension	Reasoning	Score
Specificity	It names the domain ("Freedcamp integration") and one concrete action ("Manage Organizations"), but coverage is not comprehensive — tasks, issues, projects, time, files are all absent. This matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; a 4 would require several specific actions.	3 / 5
Completeness	Both 'what' ("Freedcamp integration. Manage Organizations.") and 'when' ("Use when the user wants to interact with Freedcamp data") are present, but the 'when' is generic rather than enumerating concrete trigger phrases. Matches the 'has both what and when; when could be more explicit' anchor; not a 5 because no concrete trigger phrases are listed.	4 / 5
Trigger Term Quality	The only natural keyword is "Freedcamp" ("Use when the user wants to interact with Freedcamp data"); common variations users would say — projects, tasks, to-dos, issues — are missing. Matches 'some relevant keywords but missing common variations'; not a 4 because coverage is thin rather than merely a few terms short.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product (Freedcamp) with a product-scoped trigger gives it a clear niche with minimal overlap risk against other skills. Matches 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/freedcamp/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.