Meilisearch PHP PHPDoc Writer
meilisearch/meilisearch-php
Documents public methods of the meilisearch-php SDK with compact PHPDoc, including @see links, @since tags and the experimental-feature notice.
L5-L8 函數簽名驗證 - 檢查參數、返回值、類型提示、文檔字符串. An agent skill from peijun1700/bluemouse.
$ npx skills add peijun1700/bluemouse --skill validate-signature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install peijun1700/bluemouse validate-signature --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/peijun1700/bluemouse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/validate-signature .claude/skills/validate-signature && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "validate-signature" agent skill from https://github.com/peijun1700/bluemouse/tree/main/.claude/skills/validate-signature into .claude/skills/validate-signature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-signature", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/peijun1700/bluemouse/tree/main/.claude/skills/validate-signatureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add peijun1700/bluemouse --skill validate-signature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install peijun1700/bluemouse validate-signature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peijun1700/bluemouse.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/validate-signature .agents/skills/validate-signature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "validate-signature" agent skill from https://github.com/peijun1700/bluemouse/tree/main/.claude/skills/validate-signature into .agents/skills/validate-signature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-signature", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add peijun1700/bluemouse --skill validate-signature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install peijun1700/bluemouse validate-signature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peijun1700/bluemouse.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/validate-signature .cursor/skills/validate-signature && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "validate-signature" agent skill from https://github.com/peijun1700/bluemouse/tree/main/.claude/skills/validate-signature into .cursor/skills/validate-signature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-signature", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/peijun1700/bluemouse.git --path .claude/skills/validate-signature--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add peijun1700/bluemouse --skill validate-signature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install peijun1700/bluemouse validate-signature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peijun1700/bluemouse.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/validate-signature .gemini/skills/validate-signature && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "validate-signature" agent skill from https://github.com/peijun1700/bluemouse/tree/main/.claude/skills/validate-signature into .gemini/skills/validate-signature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-signature", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install peijun1700/bluemouse validate-signatureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add peijun1700/bluemouse --skill validate-signature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/peijun1700/bluemouse.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/validate-signature .github/skills/validate-signature && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "validate-signature" agent skill from https://github.com/peijun1700/bluemouse/tree/main/.claude/skills/validate-signature into .github/skills/validate-signature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-signature", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add peijun1700/bluemouse --skill validate-signature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install peijun1700/bluemouse validate-signature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peijun1700/bluemouse.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/validate-signature .opencode/skills/validate-signature && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "validate-signature" agent skill from https://github.com/peijun1700/bluemouse/tree/main/.claude/skills/validate-signature into .opencode/skills/validate-signature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-signature", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
validate-signatureL5-L8 函數簽名驗證 - 檢查參數、返回值、類型提示、文檔字符串. An agent skill from peijun1700/bluemouse.
Validate Signature is an agent skill from peijun1700/bluemouse. L5-L8 函數簽名驗證 - 檢查參數、返回值、類型提示、文檔字符串。 BlueMouse 17-Layer Validation Group 2。 Triggers: "signature", "參數檢查", "type hints", "docstring"
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `validator.py`).
It sits in Development, covering Technical documentation and Type safety. The licence is AGPL-3.0.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4f32ef0. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Validate Signature loads about 923 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 156 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from peijun1700/bluemouse at commit 4f32ef0, republished under its AGPL-3.0 licence (© peijun1700). 156 words, ~923 tokens.
.claude/skills/validate-signature/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.BlueMouse 17-Layer Validation System - Group 2: 函數簽名驗證
Follow the checklist below to analyze code.
python3 .claude/skills/validate-signature/validator.py myfile.py
python3 .claude/skills/validate-signature/validator.py --spec spec.json myfile.pyWhat: Function has parameters (or matches spec if provided)
How:
func = functions[0] # Check first function
actual_params = set(arg.arg for arg in func.args.args)
if spec and 'inputs' in spec:
expected_params = set(spec['inputs'])
passed = expected_params == actual_params
else:
passed = True # No spec, just report countPass:
"參數與規格匹配""函數有 N 個參數"Fail: "參數不匹配: 期望 {expected}, 實際 {actual}"
What: Function has explicit return statement
How:
has_return = any(
isinstance(node, ast.Return)
for node in ast.walk(func)
)Pass: "函數有返回值"
Fail: "函數缺少返回值"
Examples:
# ✅ PASS
def process(data):
return data * 2
# ❌ FAIL
def process(data):
print(data) # No returnWhat: Type hints coverage ≥80% AND has return type annotation
How:
params_with_hints = sum(1 for arg in func.args.args if arg.annotation)
total_params = len(func.args.args)
has_return_hint = func.returns is not None
if total_params > 0:
coverage = params_with_hints / total_params
else:
coverage = 1.0 if has_return_hint else 0.0
passed = coverage >= 0.8 and has_return_hintPass: "類型提示覆蓋率: {coverage}%"
Fail: "類型提示不足: {coverage}%"
Coverage Examples:
| Params | Annotated | Coverage | Return Type | Result |
|---|---|---|---|---|
| 5 | 5 | 100% | ✅ | ✅ PASS |
| 5 | 4 | 80% | ✅ | ✅ PASS |
| 5 | 3 | 60% | ✅ | ❌ FAIL |
| 5 | 5 | 100% | ❌ | ❌ FAIL |
Examples:
# ✅ PASS: 100% coverage + return type
def process(data: list, count: int) -> dict:
return {}
# ❌ FAIL: Missing return type
def process(data: list, count: int):
return {}
# ❌ FAIL: <80% coverage
def process(data, count: int) -> dict: # 50%
return {}What: Function has meaningful docstring (>10 characters)
How:
docstring = ast.get_docstring(func)
passed = docstring and len(docstring) > 10Pass: "有完整文檔字符串 ({length} 字符)"
Fail: "缺少或文檔字符串過短"
Examples:
# ✅ PASS: >10 characters
def process(data):
"""Process input data and return results."""
return data
# ❌ FAIL: Too short (≤10 chars)
def process(data):
"""Process"""
return data
# ❌ FAIL: No docstring
def process(data):
return data==================================================
L5-L8: 函數簽名驗證
==================================================
Status: ✅ PASSED / ❌ FAILED
Score: X/100 (N/4 layers)
✅/❌ L5: 參數檢查 - [message]
✅/❌ L6: 返回值檢查 - [message]
✅/❌ L7: 類型提示檢查 - [message]
✅/❌ L8: 文檔字符串檢查 - [message]| Skill | Layers |
|---|---|
/validate-17-layers | L1-L17 (完整) |
/validate-syntax | L1-L4 |
/validate-signature | L5-L8 |
/validate-dependencies | L9-L12 |
/validate-logic | L13-L17 |
Part of BlueMouse 17-Layer Validation System
© peijun1700, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .claude/skills/validate-signature of peijun1700/bluemouse.
Open the folder on GitHubat commit 4f32ef0
Validate Signature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Validate Signature this skillpeijun1700/bluemouse | 109 | — | ~923 | Automated safety check: Notes | AGPL-3.0 | |
| Meilisearch PHP PHPDoc Writermeilisearch/meilisearch-php | 758 | — | ~569 | Automated safety check: Pass | MIT | |
| Diataxis Docs Writercalf-ai/calfkit-sdk | 149 | 1 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Repo Guardsimovilab/databus | 101 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Adk Stylegoogle/adk-python | 22k | — | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Implement Widget Frontendcryptomilk/hass-eink-dashboard | 116 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 |
meilisearch/meilisearch-php
Documents public methods of the meilisearch-php SDK with compact PHPDoc, including @see links, @since tags and the experimental-feature notice.
calf-ai/calfkit-sdk
Write or improve software documentation using the Diátaxis framework — four documentation types (tutorials, how-to guides, reference, explanation), each serving a different user need.
simovilab/databus
Keep the databus repo clean as it grows — verify new/changed backend code meets the project's docstring, type-hint, and structural conventions, and update any docs the change made stale.
google/adk-python
Python style and codebase conventions for ADK (Agent Development Kit): private-by-default file visibility, imports, type hints, Pydantic v2 models, formatting, docstrings, logging, async I/O, file…
cryptomilk/hass-eink-dashboard
Add TypeScript types in ha.d.ts and editor schema in eink-dashboard-editor.ts for a new or updated widget type; also handles deprecating an old type (remove from picker, keep schema, add @deprecated…
wshobson/agents
Python code style, linting, formatting, naming conventions, and documentation standards.
peijun1700/bluemouse
L9-L12 依賴關係驗證 - 檢查導入語句、標準庫、第三方庫、循環依賴. An agent skill from peijun1700/bluemouse.
peijun1700/bluemouse
L13-L17 類型和邏輯驗證 - 檢查類型一致性、邏輯完整性、錯誤處理、安全性、性能. An agent skill from peijun1700/bluemouse.
peijun1700/bluemouse
L1-L4 語法和結構驗證 - 檢查 Python 語法、AST 結構、縮進格式、命名規範. An agent skill from peijun1700/bluemouse.
peijun1700/bluemouse
The BlueMouse 17-Layer Alpha Scale (Static Standard). An agent skill from peijun1700/bluemouse.
Categories
L5-L8 函數簽名驗證 - 檢查參數、返回值、類型提示、文檔字符串. An agent skill from peijun1700/bluemouse. Validate Signature is an agent skill from peijun1700/bluemouse.
Validate Signature fits situations like: tasks that involve Technical documentation; tasks that involve Type safety.
Run `npx skills add peijun1700/bluemouse --skill validate-signature -a claude-code`. Or copy the skill folder (.claude/skills/validate-signature in peijun1700/bluemouse) into .claude/skills/validate-signature in your project. Claude Code loads it when a task matches its description.
Run `npx skills add peijun1700/bluemouse --skill validate-signature -a codex`. Or copy the skill folder (.claude/skills/validate-signature in peijun1700/bluemouse) into .agents/skills/validate-signature in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add peijun1700/bluemouse --skill validate-signature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-signature, .gemini/skills/validate-signature, .github/skills/validate-signature and .opencode/skills/validate-signature in your project.
Going by SKILL.md and its folder, Validate Signature needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Validate Signature is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 923 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Validate Signature: Meilisearch PHP PHPDoc Writer (meilisearch/meilisearch-php, 758 stars), Diataxis Docs Writer (calf-ai/calfkit-sdk, 149 stars), Repo Guard (simovilab/databus, 101 stars) and Adk Style (google/adk-python, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
peijun1700 (a GitHub user) maintains it in peijun1700/bluemouse, which has 109 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on January 29, 2026.
Source: peijun1700/bluemouse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.