Name: bigpictureio
Rating: 61.6 (1 reviews)
Author: membranedev

bigpictureio

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

Quality

72%

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

Quality

Content

82%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 a strong, executable guide to driving Bigpicture.io through the Membrane CLI, with a clear state-aware connection workflow and concrete commands throughout. It could improve by tightening a few explanatory asides and giving a fuller error-recovery path for setup failures.

Suggestions

Add an explicit retry/recovery step for CONFIGURATION_ERROR and SETUP_FAILED (e.g., inspect the error field, fix config, then re-run `membrane connection ensure` and re-poll) to close the workflow's feedback loop.

Trim editorial asides like 'so you can focus on the integration logic rather than auth plumbing' to keep the body lean and assume Claude's competence.

Move the long inline entity bullet list (Story, Roadmap, Team, ... Webhook) into a references/ entities file and link to it, keeping the main SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, leading with executable CLI commands and only brief necessary explanations of the auth/connection flow, with minor instances of editorializing ('so you can focus on the integration logic rather than auth plumbing').	4 / 5
Actionability	Provides copy-paste-ready commands for the full lifecycle — install, login, connection ensure, connection get --wait, action list/run, and request proxying — with concrete flags and example parameters covering common cases.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with explicit state-based checkpoints and a poll-after-user-action feedback loop (BUILDING -> READY / CLIENT_ACTION_REQUIRED -> re-poll), though error recovery for CONFIGURATION_ERROR/SETUP_FAILED stops at 'check the error field' without a retry path.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-sectioned (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with the entity list serving as a navigable overview, though the long inline entity bullet list could be split into a reference file.	4 / 5
	Total	17 / 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 answers both what the skill does and when to use it, anchored to a specific named app. Its main weaknesses are generic action verbs and a thin, single trigger phrase rather than richer natural keywords.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Bigpicture.io actions like 'plan and track projects, manage roadmaps, teams, risks, and tasks' so capabilities are explicit.

Expand the trigger phrase to cover natural user expressions: 'Use when the user wants to plan projects, build roadmaps, manage teams/iterations, or track tasks and risks in Bigpicture.io'.

Consider mentioning key entity names (roadmap, team, task, risk) as trigger terms so the skill surfaces for the specific jobs users describe.

Dimension	Reasoning	Score
Specificity	Names the Bigpicture.io domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are fairly generic and not a comprehensive list of concrete actions.	3 / 5
Completeness	Explicitly states both the 'what' (manage data, records, automate workflows) and a 'when' ('Use when the user wants to interact with Bigpicture.io data'), though the trigger guidance is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes one natural trigger phrase ('Use when the user wants to interact with Bigpicture.io data') but lacks common variations, synonyms, or entity-related terms users would actually say.	3 / 5
Distinctiveness Conflict Risk	The named app Bigpicture.io gives a clear niche with minimal overlap risk, though 'manage data, records' is broad enough to leave a little ambiguity with adjacent project-management skills.	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/bigpictureio/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.