Name: limacharlie
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

limacharlie

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/limacharlie/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 CLI usage guidance is concrete, executable, and sequenced with useful state-checkpoint feedback, but the document is dominated by a massive inlined glossary of generic security terms that pads the context without aiding execution. Removing that glossary would dramatically improve token efficiency.

Suggestions

Delete the ~280-line security-terms glossary under "LimaCharlie Overview"; Claude already knows these concepts and they do not map to Membrane actions or parameters.

Add one fully resolved end-to-end example (real actionId + CONNECTION_ID + --input) so the run/proxy flow is copy-paste ready without guessing placeholders.

Move any genuinely needed entity/parameter reference into a references/ file and link to it one level deep, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~280-line "LimaCharlie Overview" glossary (e.g., "DNA Hacking", "Brain Hacking", "Space Hacking", "Cyber Warfare") is heavy padding of concepts Claude already knows, though the CLI sections themselves are lean.	2 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, auth, connection, action search/run, and proxying, with only minor gaps (placeholders like CONNECTION_ID and actionId are never shown with a resolved end-to-end example).	4 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence exists with explicit state-checkpoint polling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop; minor gaps in step labeling ("Step 2"/"1b").	4 / 5
Progressive Disclosure	Section headers give reasonable structure and no nested references exist, but the large glossary is inlined monolithic content that should be separated or removed, and there are no bundle files to offload detail into.	3 / 5
	Total	13 / 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 answers both what and when with an explicit trigger clause and is highly distinct thanks to the product name, but its capability phrasing is generic and trigger-term coverage is narrow. Tightening the action list and adding a few natural trigger phrasings would lift it.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete LimaCharlie-specific actions (e.g., "query sensors, manage detection rules, run hunts, review audit logs").

Broaden trigger terms beyond "LimaCharlie data" to natural phrasings users say (e.g., "LimaCharlie sensors, detections, hunts, or D&R rules").

Dimension	Reasoning	Score
Specificity	Names the domain ("LimaCharlie integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete and coverage is not comprehensive.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with LimaCharlie data") are present, though the "what" is somewhat generic.	4 / 5
Trigger Term Quality	The only natural trigger terms are "LimaCharlie" and "LimaCharlie data"; relevant but missing common variations or synonyms a user might say.	3 / 5
Distinctiveness Conflict Risk	The distinctive product name "LimaCharlie" gives it a clear niche with minimal overlap risk against other skills.	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/limacharlie/SKILL.md
Commit: f484c82

Reviewed: 6 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.