SKILLEMALL.ai

FC gajago-sns

경기도교육청 취창업지원센터 SNS 콘텐츠 자동 생성. /가자고 명령어로 텍스트/키워드/이미지를 입력하면 인스타그램, 페이스북, 밴드용 카피 + 이미지 + 20초 영상을 자동 생성. Trigger on /가자고 command.

Not recommendedcritical or high security findings · low grade F
ClawHub Agent Skills author: sang-su0916 v1.0.1 MIT-0 10 files body ≈ 1 164 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
F
38/100
safety, quality, tests
Safety 60%
13
Quality 40%
75
Run on models
none yet
Process rating
C
52/100
Has gaps
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

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Secrets in code
If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
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 · 11

  • high Secrets in code secret-google-key autoresearch-gajago-sns/gajago-sns-v2.md:55
    Google API key
    GEMINI_API_KEY=AIza…0vM \
  • high Secrets in code secret-google-key autoresearch-gajago-sns/gajago-sns-v2.md:90
    Google API key
    GEMINI_API_KEY=AIza…0vM \
  • high Secrets in code secret-google-key SKILL.md:55
    Google API key
    GEMINI_API_KEY=AIza…0vM \
  • high Secrets in code secret-google-key SKILL.md:90
    Google API key
    GEMINI_API_KEY=AIza…0vM \
Medium and low: 7
  • medium Secrets in code secret-google-key autoresearch-gajago-sns/gajago-sns-v2.md:121
    Google API key (quoted — discussed, not commanded)
    - `GEMINI_API_KEY=AIza…0vM`
    quoted
  • medium Secrets in code secret-google-key SKILL.md:121
    Google API key (quoted — discussed, not commanded)
    - `GEMINI_API_KEY=AIza…0vM`
    quoted
  • low Secrets in code secret-high-entropy-token autoresearch-gajago-sns/test-input.md:18
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    - Kaka…-48 001.jpeg
    fixture
  • low Secrets in code secret-high-entropy-token autoresearch-gajago-sns/test-input.md:19
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    - Kaka…-49 002.jpeg
    fixture
  • low Secrets in code secret-high-entropy-token autoresearch-gajago-sns/test-input.md:20
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    - Kaka…-50 003.jpeg
    fixture
  • low Secrets in code secret-high-entropy-token autoresearch-gajago-sns/test-input.md:21
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    - Kaka…-51 004.jpeg
    fixture
  • low Secrets in code secret-high-entropy-token autoresearch-gajago-sns/test-input.md:22
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    - Kaka…-52 005.jpeg
    fixture

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

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 52/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
  • 0Progress reporting. Says nothing while it works
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1164 tokens
  • 100Running it twice. No mutating operations

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
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -2localhost URLs: will not work for another user
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 125: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (9 code blocks)

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

External checks

ClawHub: suspicious
The skill has a plausible SNS automation purpose, but it exposes a Gemini API key and gives broad, poorly scoped authority to run local tools, use fixed personal paths, and send generated content externally.
LLM: suspicious (high) · VirusTotal: · 29 May 2026