SKILLEMALL.ai

AC saas-gateway

Unified SaaS integration gateway via api.aisa.one (AISA gateway, v3.1): manage OAuth auth for third-party SaaS apps (Gmail/Slack/GitHub/Notion etc.), tool execution, tool-router sessions, triggers, webhooks, MCP servers, and usage stats. Use when connecting third-party SaaS accounts, running cross-SaaS tools, managing MCP servers, setting up triggers, or checking usage. Keywords: SaaS gateway, connect app, OAuth link, run tool, auth config, tool router, MCP server, trigger, webhook, connected account, usage stats

ClawHub Agent Skills author: bibaofeng v1.0.0 MIT-0 9 files body ≈ 4 045 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions

IntegrationNotionSlackGmailGitHubAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "homepage"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "primaryEnv"
    • note frontmatter-key unknown frontmatter key "requires"

    Process rating: all ten parameters 60/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70Execution cost. Instruction body is 4045 tokens
    • 100Steps. 81 steps
    • 100Failures and branches. 5 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 11 top-level sections: this looks like several domains in one skill

    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)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 518: enough signal without eating the budget
    • +4Structure: 18 headings
    • +3Step-by-step instructions: 81 items
    • +4Has examples (5 code blocks)
    • +4Reference files are cited in the instructions (6 of 6)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This SaaS gateway is coherent and not deceptive, but it gives broad control over connected third-party accounts and sensitive gateway resources with incomplete per-action guardrails.
    LLM: suspicious (high) · 28 May 2026