Name: microsoft-power-bi
Rating: 58.4 (1 reviews)
Author: membranedev

microsoft-power-bi

Microsoft Power BI integration. Manage Reports, Workspaces, Apps, Users. Use when the user wants to interact with Microsoft Power BI data.

Quality

68%

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/microsoft-power-bi/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 concrete executable membrane CLI commands and a well-sequenced connection workflow including state handling and polling. Its weaknesses are some avoidable Power BI background prose and a lack of validation/confirmation guidance for the destructive delete actions.

Suggestions

Trim the opening paragraph that explains what Power BI is and who uses it; Claude already knows this and it competes with the token budget.

Add an explicit validation/confirmation step before running destructive actions (Delete Workspace, Delete Dataset, Delete Report) to lift workflow clarity past the destructive-operation cap.

Consider moving the Popular actions table into a references file (e.g. ACTIONS.md) and summarizing the few most-used actions inline, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete membrane commands, but the opening paragraph explains what Power BI is and who uses it ("used by data analysts, business users, and IT professionals") which Claude already knows, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready membrane commands for install, login, connection ensure/get with --wait, action list/run, and proxy requests, plus a flags table and JSON-input example, covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling, but destructive operations (Delete Workspace, Delete Dataset, Delete Report) appear in the actions table with no confirm/validation step, and the rubric caps destructive/batch skills without validation at 3.	3 / 5
Progressive Disclosure	The single self-contained file is organized into clear sections (Overview, Working with, Popular actions table, Best practices) with no nested references; it stops short of 5 only because the large Popular actions table and flag details could be split into a reference file for leaner top-level loading.	4 / 5
	Total	15 / 20 Passed

Description

67%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 is solid: it names the product domain, lists four concrete managed entities, and includes an explicit 'Use when' trigger in third-person voice. The main weakness is that the trigger phrasing is generic and lacks synonyms or format-specific terms that would sharpen when-to-use matching.

Suggestions

Add concrete trigger synonyms and surface terms (e.g., 'Power BI reports, datasets, dashboards, workspaces') so the skill matches more natural user phrasings.

Make the 'when' clause more specific by naming the actual interactions users request (e.g., 'Use when listing, creating, refreshing, or deleting Power BI reports, datasets, or dashboards').

Expand the 'what' beyond the four entities to the actions performed (create, list, update, delete, refresh) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Manage Reports, Workspaces, Apps, Users" names the domain and several concrete managed entities, matching the 'several specific actions; minor gaps' anchor; it falls short of 5 because it does not enumerate the full range of concrete operations.	4 / 5
Completeness	It answers both 'what' (manage Reports, Workspaces, Apps, Users) and 'when' ("Use when the user wants to interact with Microsoft Power BI data"), but the 'when' trigger phrasing is fairly generic rather than highly specific, fitting the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Microsoft Power BI data" gives one natural trigger phrase and the product name, but lacks common synonyms or file/format variations, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	It is tied to the named Microsoft Power BI product with distinct triggers, giving mostly-distinct niche with only minor overlap risk against other BI/integration skills.	4 / 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/microsoft-power-bi/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.