Agent Skills
› yaojingang/GEORank
› georank
georank
GitHub通过HTTP API操作和管理自托管GEOrank实例,涵盖登录认证、账号检查、数据提交与诊断、关键词扩展及管理员权限控制,严格遵循安全边界与审计流程。
触发场景
需要登录或检查GEOrank账户状态
执行GEOrank数据读写或管理操作
运行GEO诊断或管理解决方案对话
安装
npx skills add yaojingang/GEORank --skill georank -g -y
SKILL.md
Frontmatter
{
"name": "georank",
"description": "Operate and manage a self-hosted GEOrank instance through its HTTP API. Use when asked to log in, inspect a GEOrank account, submit or manage companies, run or read GEO diagnostics, manage solution conversations, expand keywords, inspect usage, or perform authenticated GEOrank administrator work across users, content, experts, providers, modules, homepage releases, and settings. Login guidance defaults to an ordinary user and unlocks administrator actions only after \/api\/auth\/me returns role=admin. Do not use for general GEO strategy, article writing, SEO advice, or GEOrank code development that does not operate a running instance."
}
GEOrank Operator
Workflow
Resolve every relative path below from this Skill directory, independent of the caller's current workspace.
- Confirm the target GEOrank base URL. Use
http://localhost:8000only for a local instance; require HTTPS for remote instances. - Resolve authentication:
- Treat login as an ordinary-user flow and never ask the user to choose a role.
- Run
python3 scripts/georank_client.py login --account <account>when no session exists. - Run
python3 scripts/georank_client.py whoamiafter login. Enable administrator branches only when the returned role isadmin; treatenterpriseas a regular authenticated user.
- Read
references/user-capabilities.mdfor public and user-owned operations. Readreferences/admin-capabilities.mdonly for administrator requests. - For reads, call the API directly with
scripts/georank_client.py call GET <path>. - For writes, run the same command without
--executefirst and show the preflight result. Execute only after the user's request clearly authorizes that exact change. - Before any administrator mutation, read
references/safety-policy.mdand supply its required confirmation phrase. Never infer administrator authority from the wording of a request. - Return an execution receipt containing the action, status, resource identifiers, request ID when present, and the next safe step. Remove passwords, tokens, API keys, and other secrets from all output.
Safety Boundary
- Never pass passwords or tokens as command-line arguments. Login reads
GEORANK_PASSWORDor uses a hidden terminal prompt; API calls readGEORANK_TOKENor the private session file. - Never expose, copy, or persist a secret outside the session store managed by the client.
- Treat every non-read call as a side effect.
--executeis required. - Require
APPLY_ADMIN_CHANGEfor administrator writes andDELETE:<api-path-with-query>for deletions. - Stop when the detected role lacks permission, the target resource is ambiguous, or rollback information is unavailable for a high-impact change.
Output Contract
Return a compact Markdown or JSON receipt with:
- detected access level: public, user, or admin
- operation and target resource
- dry-run or executed status
- API status, resource IDs, and request ID when available
- redacted change summary and next step
- rollback guidance for administrator changes
Reference Map
references/user-capabilities.md: public and ordinary-user operations.references/admin-capabilities.md: administrator operation groups and confirmation requirements.references/safety-policy.md: authentication, secrets, side effects, polling, and rollback rules.scripts/georank_client.py: deterministic login, session, role detection, preflight, and API execution.evals/trigger_cases.json: routing positives, negatives, and near neighbors.examples/request_payloads.json:file-backed fixtureexamples listed byinput_files.reports/output-risk-profile.md: likely output failures and repair checks.reports/output_quality_scorecard.md: current output and verification evidence.reports/security_trust_report.md: generatedtrust reportafter validation.
版本历史
- 21d1ab9 当前 2026-07-19 08:50


