Name: fogbugz
Rating: 59.2 (1 reviews)
Author: membranedev

fogbugz

FogBugz integration. Manage Persons, Organizations, Leads, Deals, Projects, Pipelines and more. Use when the user wants to interact with FogBugz data.

Quality

69%

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

Quality

Content

63%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 a well-sequenced connect-and-act workflow, but it is held back by inlined bulk (especially the actions table) that should live in a reference file, some concept padding, and a broken 'Step 2' cross-reference.

Suggestions

Extract the 'Popular actions' table (and the proxy flag reference) into a referenced file such as references/actions.md and link to it from SKILL.md to improve progressive disclosure.

Fix the broken 'skip to Step 2' / '1b' labeling: either define a labeled Step 2 section or reword to 'skip to Searching for actions'.

Trim concept-level padding (e.g. 'FogBugz is a project management and bug tracking system...') and the duplicated auth examples to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but it includes mild concept padding ('FogBugz is a project management and bug tracking system...'), repeated auth examples, and a 19-row 'Popular actions' table that inflates tokens; could be tightened and offloaded.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with flag tables, but some examples leave placeholder tokens like CONNECTION_ID unfilled, a minor gap below fully executable.	4 / 5
Workflow Clarity	A clear sequenced flow (install -> auth -> connect -> poll state -> search -> run) with real checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after user action, check CONFIGURATION_ERROR), but the 'skip to Step 2' / '1b' labels reference a Step 2 that is never defined, leaving a navigation gap.	4 / 5
Progressive Disclosure	Sections are present and ordered, but the skill is a ~166-line monolith with no bundle files; the large Popular actions table and the proxy flag reference are inlined content that clearly belongs in a separate one-level-deep reference file, and no such references are signaled.	3 / 5
	Total	14 / 20 Passed

Description

75%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 cleanly answers both what and when and is anchored to a distinct product name, but its trigger phrases are generic and it omits the FogBugz-native vocabulary (cases, bugs) a user would actually say. Strong but not exemplary.

Suggestions

Replace the generic 'Use when the user wants to interact with FogBugz data' with concrete triggers like 'Use when the user wants to create, search, edit, or close FogBugz cases, or manage projects, areas, and milestones'.

Add FogBugz-native terms (cases, bugs, tickets, FixFor/milestones) so natural user phrasing matches the description.

Drop or reconcile the CRM-style entities (Leads, Deals, Pipelines) if they are not actually part of FogBugz to reduce conflict risk with CRM skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete managed entities ('Manage Persons, Organizations, Leads, Deals, Projects, Pipelines'), with the generic 'and more' tail leaving minor coverage gaps that keep it below a 5.	4 / 5
Completeness	It states both what ('FogBugz integration. Manage ...') and when ('Use when the user wants to interact with FogBugz data'), but the 'when' clause is generic rather than listing concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Good keyword coverage via the entity list plus the product name 'FogBugz' and trigger 'interact with FogBugz data', though the most natural FogBugz-specific terms a user would say (cases, bugs, tickets) are absent.	4 / 5
Distinctiveness Conflict Risk	The 'FogBugz integration' framing names a specific product giving a clear niche with low conflict risk, but the CRM-flavored entity list (Leads, Deals, Pipelines) introduces minor overlap ambiguity with CRM skills, keeping it at 4.	4 / 5
	Total	16 / 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/fogbugz/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.