Name: bigtincan
Rating: 58.4 (1 reviews)
Author: membranedev

bigtincan

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

Quality

67%

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

Quality

Content

68%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 content is highly actionable with copy-paste-ready Membrane commands and a well-structured connection workflow with state validation. Weaknesses are marketing-style padding in the overview and the absence of verification steps after running potentially destructive actions.

Suggestions

Add a verification step after `membrane action run`, e.g. re-query or inspect the `output` field to confirm the action succeeded before reporting completion to the user.

Trim the introductory Bigtincan marketing paragraph to a one-line domain summary so the skill assumes Claude's competence and respects the token budget.

Move the proxy flag reference table into a separate reference file linked from the body to improve progressive disclosure now that the skill exceeds 50 lines.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the marketing-style overview ("It helps sales and service teams... improve sales performance and customer engagement") and phrases like "so you can focus on the integration logic rather than auth plumbing," fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request proxy) with concrete flags and JSON examples, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with state polling and error-state handling, but running actions on external data (create/update/delete records, automate workflows) is potentially destructive/batch with no post-run verification step, triggering the cap that limits workflow clarity to 3.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear labeled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, but at over 50 lines with no external bundle files it is not maximally split, sitting below the top anchor.	4 / 5
	Total	15 / 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 benefits from Bigtincan being a distinct named product. Its main weakness is generic action verbs and limited trigger-term variety beyond the product name itself.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Search, read, create, and update Bigtincan stories, spaces, groups, and users" to lift specificity.

Add broader trigger phrases users might say, such as "sales content," "Hub stories," or "Bigtincan records" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Bigtincan domain plus a few actions, but the actions are generic (manage/automate) rather than concrete, matching the anchor for domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Bigtincan data"); the when clause is explicit but could be more specific with additional trigger phrases, so it sits below the top anchor.	4 / 5
Trigger Term Quality	The only natural trigger keyword is "Bigtincan" (and "Bigtincan data"), which is relevant but lacks common variations or synonyms a user might say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Bigtincan is a named product niche with distinct triggers, so it is clearly distinguishable from other skills with minimal overlap risk, matching the clear-niche 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/bigtincan/SKILL.md
Commit: f484c82

Reviewed: ~3 hours 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.