granola-multi-env-setup

Configure Granola across multiple workspaces and teams with SSO/SCIM provisioning. Use when setting up department-level workspaces, configuring user provisioning, or managing enterprise-scale Granola deployments. Trigger: "granola workspaces", "granola multi-team", "granola SSO", "granola SCIM", "granola organization setup".

Quality

79%

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 ./plugins/saas-packs/granola-pack/skills/granola-multi-env-setup/SKILL.md

Quality

Content

71%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.

A well-structured, actionable enterprise setup guide with clear sequencing and a validation checklist. Its main weakness is progressive disclosure: a reference bundle file exists but is not linked from the body, and the body inlines content that overlaps it.

Suggestions

Link references/workspace-configs.md from the body (e.g. in a '## Reference' or under relevant steps) so the bundle file is discoverable and clearly signaled.

Move detailed per-workspace config templates (SSO group mappings, compliance YAML) into the reference file and reference it, keeping the body as an overview.

Interleave small validation checkpoints between deployment steps rather than consolidating all validation into the final Step 7 checklist.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, relying on compact tables for topology, integrations, roles, and error handling rather than prose. A few sentences pad what Claude could infer (e.g. 'Each workspace operates as an isolated unit with its own folders, integrations, sharing rules, and retention policies'), keeping it just below a 5.	4 / 5
Actionability	Provides concrete, specific guidance — UI paths ('Organization Settings > Security > SSO'), exact SCIM endpoints, group-to-workspace mappings, and role matrices. As an instruction-only skill the absence of code is not penalized, but a few steps remain high-level ('Configure in your IdP'), so it is not fully copy-paste ready.	4 / 5
Workflow Clarity	Seven steps are clearly sequenced and Step 7 includes an explicit validation checklist plus an error-handling table for recovery. Because validation is consolidated at the end rather than interleaved as per-step checkpoints, it does not reach the 5-anchor's 'explicit validation steps' embedded throughout.	4 / 5
Progressive Disclosure	The body is well-sectioned, but a bundle file (references/workspace-configs.md) exists and is never referenced from the body, while substantial overlapping detail (SSO group mapping, compliance config) is inlined. References are present on disk but not clearly signaled, matching the 3-anchor.	3 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong description: third-person voice, clear what/when structure, and explicit trigger phrases tied to a specific product niche. Minor room to broaden trigger synonyms and surface more setup sub-tasks.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Configure Granola across multiple workspaces and teams with SSO/SCIM provisioning' and 'configuring user provisioning' — but coverage is not exhaustive of all setup activities. It sits above the 3-anchor (1-2 concrete actions) due to multiple specific actions, but below 5 because several sub-tasks (compliance, integrations, roles) are not surfaced in the description.	4 / 5
Completeness	Explicitly answers both 'what' ('Configure Granola across multiple workspaces and teams with SSO/SCIM provisioning') and 'when' ('Use when setting up department-level workspaces, configuring user provisioning, or managing enterprise-scale Granola deployments') with concrete trigger phrases, matching the 5-anchor.	5 / 5
Trigger Term Quality	Provides a dedicated Trigger list — 'granola workspaces', 'granola multi-team', 'granola SSO', 'granola SCIM', 'granola organization setup' — which are natural phrases a user might say. Coverage is good and product-specific, but a few common synonyms or variations are absent, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — enterprise Granola multi-workspace/SSO/SCIM setup — with distinct product-specific triggers, minimizing overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/granola-pack/skills/granola-multi-env-setup/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.