slack-admin-api

Enterprise Grid Admin API operations with the Slack Go SDK. Use when managing organization-wide conversations, assigning or listing admin roles, configuring team settings, restricting channel access, or building internal tooling for Slack workspace/org administrators.

Quality

85%

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

Quality

Content

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

Excellent token efficiency and actionability — nearly the whole body is executable, SDK-accurate Go with zero padding. The two weaknesses are operational: destructive/bulk operations ship with no validation or verification workflow, and the single external reference points outside the skill bundle to a file that is not present, so progressive disclosure breaks in practice.

Suggestions

Fix the reference link to point inside the skill bundle (e.g., references/admin-api-reference.md) and ship that file, so the 'full conversations, roles, and teams surface' pointer actually resolves.

Add a validation step for destructive and bulk operations — e.g., list and confirm channel IDs with AdminConversationsSearch or AdminConversationsRestrictAccessListGroups before AdminConversationsBulkDelete, and check each call's error before proceeding to the next.

Include a brief recover pattern for failed bulk operations (retry semantics for partially completed BulkMove/BulkArchive batches) to turn the irreversible-operation warning into an actionable workflow.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: ~110 lines of almost pure executable Go with no padding, no explanation of concepts Claude already knows (what Slack or Go is, how SDKs work). Every section, including 'Prerequisites' and the TeamDiscoverability enumeration, adds information Claude would not reliably know.	5 / 5
Actionability	Fully executable, copy-paste-ready code using real SDK methods, params structs, and option functions (e.g., AdminConversationsSetTeamsParams, AdminRolesListAssignmentsOptionRoleIDs, TeamDiscoverabilityInviteOnly). Concrete examples cover the common cases for every section.	5 / 5
Workflow Clarity	The rubric caps workflow clarity at 3 for skills with destructive or batch operations that lack validation/verification steps. The body includes irreversible operations (AdminConversationsDelete, AdminConversationsBulkDelete, BulkArchive) with no verify-before-act, confirm, or error-recovery loop — only a one-line pitfall warning. Without that cap the single, unambiguous actions would score higher, but the cap takes precedence.	3 / 5
Progressive Disclosure	Section structure is clean and the pointer is well signaled ('See admin-api-reference.md for the full conversations, roles, and teams surface, including retention, EKM, and invite/lookup methods'), but the link path is ../../references/admin-api-reference.md, which escapes the skill directory, and no references/ bundle exists — the referenced file does not resolve, breaking navigation. Structure is present, but the reference layer does not actually work.	3 / 5
	Total	16 / 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: it names the domain and SDK, enumerates concrete capability areas, and provides an explicit 'Use when' clause with natural trigger phrases. Only minor gaps in named operations keep specificity and trigger coverage just below the top anchors.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('assigning or listing admin roles', 'configuring team settings', 'restricting channel access') alongside the domain ('Enterprise Grid Admin API operations with the Slack Go SDK'). Minor gaps: archive/rename/bulk-delete conversation operations are only subsumed under 'managing organization-wide conversations', keeping it below the comprehensive anchor 5 but well above the 1-2-action anchor 3.	4 / 5
Completeness	Explicitly answers both what ('Enterprise Grid Admin API operations with the Slack Go SDK' plus a concrete action list) and when ('Use when managing organization-wide conversations, assigning or listing admin roles, ...'), matching the anchor-5 pattern of concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage including synonyms ('workspace/org administrators', 'organization-wide conversations', 'channel access', 'admin roles'). A few natural terms users might say are missing (e.g., 'archive channels', 'bulk operations'), so it sits between anchor 3 and the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche — org-level Enterprise Grid administration via the Slack Go SDK with an org-admin token — with distinct triggers; minimal risk of firing for regular bot-API or OAuth work.	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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: freightCognition/linehaulai-claude-marketplace
Path: plugins/slack-go-sdk/skills/slack-admin-api/SKILL.md
Commit: 88571a6

Reviewed: 5 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.