This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Renamed to creator-skill-v2
skill-service
Standalone Creator SKILL service — MCP + REST API + independent billing.
Quick start
cd apps/skill-service
python -m venv .venv
.venv/Scripts/python -m pip install -U pip
.venv/Scripts/pip install -e .
cp .env.example .env # edit database / modash keys
.venv/Scripts/python scripts/init_db.py
.venv/Scripts/python scripts/seed_dev_account.py --email dev@demo.com --password "12345678" --credits 5000
.venv/Scripts/python main.py
Health: GET http://127.0.0.1:8080/health
MCP: http://127.0.0.1:8080/mcp (Bearer sk_live_...)
Production
- Release (Stripe only): docs/PRODUCTION_RELEASE.md
- Prod deploy script:
python scripts/deploy_prod_server.py(usesprod.yaml+.env_prod) - Deploy: docs/DEPLOY_CHECKLIST.md
- Local dev:
docker compose -f docker-compose.dev.yml up -d --buildorscripts/dev_up.ps1 -Build - Payments: docs/PAYMENT_CALLBACKS.md
- Payment E2E (Plan A/C): docs/PAYMENT_E2E_TEST.md
- Subscription E2E: docs/SUBSCRIPTION_E2E_TEST.md
- OpenClaw + ClawHub E2E: docs/OPENCLAW_E2E_TEST.md
- Stripe 测试环境配置: docs/STRIPE_TEST_ENV_SETUP.md
- MCP Registry: output/registry/
- Coze HTTP SOP:
deinai_backend/output/coze/PATH-A-SOP.md
Stdio bridge (Cursor / Claude Desktop)
export SKILL_TOKEN="sk_live_..."
skill-service-match
# or: uvx --from skill-service skill-service-match
Optional: SKILL_MCP_URL (default https://skill.deinai.ai/mcp).
Status
- Independent account / session (
sk_sess_) / API token (sk_live_) - Wallet, recharge, consumption ledger
- Portal (
/portal/): login, recharge, mock checkout, token management - Payment checkout:
POST /recharge/ordersreturnspayParams(mock / wechat / alipay) - MCP tools:
ping,get_location_ids,searchInfluencers - REST:
GET /api/v1/account/status,POST /api/v1/search/influencers - Admin: credit packages, consume rules, audit logs
Metadata
Release files for skill-service 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| skill_service-0.2.0.tar.gz | 99.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skill_service-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 186.0 kB
Release files / skill_service-0.2.0.tar.gz
| Download URL | skill_service-0.2.0.tar.gz |
|---|---|
| Size | 99.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc44516a1497b64620124c30f75669a9ada8adea2a92bd9c1158bd01c791684c
|
|
BLAKE2b-256 checksum How to use checksums |
995e2e337e179659024d86228a9d14ee28c1b05971ad6f5ed4bc8c30ca3bf28b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / skill_service-0.2.0-py3-none-any.whl
| Download URL | skill_service-0.2.0-py3-none-any.whl |
|---|---|
| Size | 86.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42114b73de41058b65e9795e51a84b0e3f40345b8b3db5d7e1f1b5894baf8a4f
|
|
BLAKE2b-256 checksum How to use checksums |
8d3dd66eaac31f9ca09734c8b325f306f2cb671fc1807e75ee9a0251584a5e29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for skill-service 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.