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".
77
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/granola-pack/skills/granola-multi-env-setup/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly defines its scope around enterprise Granola configuration with SSO/SCIM provisioning. It includes explicit 'Use when' guidance and enumerated trigger terms, making it easy for Claude to select appropriately. The description is concise, uses third-person voice, and covers both capabilities and activation conditions thoroughly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring across multiple workspaces and teams, SSO/SCIM provisioning, setting up department-level workspaces, configuring user provisioning, and managing enterprise-scale deployments. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure Granola across workspaces/teams with SSO/SCIM) and 'when' (explicit 'Use when' clause covering department-level workspaces, user provisioning, enterprise-scale deployments), plus explicit trigger terms. | 3 / 3 |
Trigger Term Quality | Includes natural, specific keywords users would say: 'granola workspaces', 'granola multi-team', 'granola SSO', 'granola SCIM', 'granola organization setup'. These are terms an enterprise admin would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: enterprise-level Granola configuration with SSO/SCIM. The combination of the specific product name 'Granola' with enterprise provisioning concepts makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has a well-structured workflow with clear sequencing and a solid validation checklist, but it is significantly over-verbose. The extensive hypothetical tables (workspace planning, integration mapping, compliance settings per department) consume many tokens providing organizational consulting advice rather than actionable technical configuration. The actionability is moderate — navigation paths are specific but much content appears speculative about Granola's actual admin interface capabilities.
Suggestions
Drastically reduce the hypothetical example tables (workspace planning, integration mapping) to 1-2 rows each as illustrations, rather than providing full organizational templates that Claude can generate on its own.
Move the detailed per-workspace compliance settings table and role hierarchy table into separate reference files, keeping only the key principles and the sensitive workspace hardening block inline.
Verify and clarify which URLs, endpoints, and UI paths are actual Granola features vs. hypothetical — mark speculative content clearly or remove it to avoid misleading Claude.
Remove explanatory content Claude already knows (e.g., what SAML 2.0 and OIDC are, what SCIM does, principle of least privilege) to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with extensive tables that appear to be hypothetical examples rather than actionable configuration. Much of the content (workspace planning tables, role hierarchies, integration mapping) is organizational advice that Claude doesn't need spelled out in this detail. The example workspace structures (Engineering, Sales, HR, etc.) are filler that pad the token count significantly. | 1 / 3 |
Actionability | The skill provides specific URLs for SSO/SCIM endpoints and step-by-step navigation paths (e.g., 'Organization Settings > Security > SSO'), which is helpful. However, much of the content describes UI navigation rather than executable commands, and the configuration details appear to be speculative/hypothetical rather than verified against actual Granola APIs or admin interfaces. | 2 / 3 |
Workflow Clarity | The 7-step sequence is logically ordered with clear dependencies (plan → create → configure SSO → integrations → compliance → roles → validate). Step 7 includes an explicit validation checklist with specific verification items and ongoing monitoring cadence, providing good feedback loops for this type of administrative setup. | 3 / 3 |
Progressive Disclosure | The content is largely monolithic — all configuration details for every workspace type are inline rather than split into separate reference files. The tables for compliance controls, role permissions, and integration mappings could be in referenced files. There is a 'Next Steps' pointer to another skill, but the main body would benefit from splitting detailed per-workspace configs into separate references. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
70e9fa4
- Reviewed
Table of Contents
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.