SKILLEMALL.ai

DD identity-access-management

Set up and manage SSO, SCIM provisioning, and MFA for startup teams using Google Workspace, Okta, or Azure AD.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 3 010 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Set up and manage SSO, SCIM provisioning, and MFA for startup teams using Google Workspace, Okta, or Azure AD.

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationAzureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
75/100
safety, quality, tests
Safety 60%
69
Quality 40%
83
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: identity-access-management (sickn33/agentic-awesome-skills)

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 7

    ✓ No critical or high findings

    Medium and low: 7
    • medium Exfiltration net-credential-use references/details.md:34
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Authorization: Bearer ${SLACK_SCIM_TOKEN}" \
    • medium Exfiltration net-credential-use references/details.md:101
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Authorization: Bearer ${SCIM_TOKEN}" \
    • medium Exfiltration net-credential-use references/details.md:230
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Authorization: SSWS ${OKTA_API_TOKEN}" \
    • medium Exfiltration net-credential-use references/details.md:323
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Authorization: SSWS ${OKTA_API_TOKEN}" \
    • medium Exfiltration net-credential-use references/details.md:328
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Authorization: Bearer ${ACCESS_TOKEN}" \
    • medium Exfiltration net-credential-use SKILL.md:148
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Authorization: SSWS ${OKTA_API_TOKEN}" \
    • low Secrets in code secret-high-entropy-token references/details.md:83
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      --principal-id "a1b2…001"
      quoted

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"
    • note edit-residue the text marks something as outdated (lines 313, 319): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 45/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 19 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3010 tokens
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Description length 110: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 19 items
    • +4Has examples (12 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.