loa-credentials — discord loa-credentials, loa-freeside, community, discord, ide skills, telegram, Claude Code, Cursor, Windsurf

v1.0.0

このスキルについて

Multi-tenant SaaS platform for token-gated onchain communities - wallet scoring, Discord/Telegram integration, and human-in-the-loop approval workflows

# Core Topics

0xHoneyJar 0xHoneyJar
[7]
[0]
Updated: 3/25/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 1/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Review Score
1/11
Quality Score
42
Canonical Locale
en
Detected Body Locale
en

Multi-tenant SaaS platform for token-gated onchain communities - wallet scoring, Discord/Telegram integration, and human-in-the-loop approval workflows

このスキルを使用する理由

Multi-tenant SaaS platform for token-gated onchain communities - wallet scoring, Discord/Telegram integration, and human-in-the-loop approval workflows

おすすめ

Suitable for operator workflows that need explicit guardrails before installation and execution.

実現可能なユースケース for loa-credentials

! セキュリティと制限

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The page lacks a strong recommendation layer.
  • - The page lacks concrete use-case guidance.
  • - The page lacks explicit limitations or caution signals.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is loa-credentials?

Multi-tenant SaaS platform for token-gated onchain communities - wallet scoring, Discord/Telegram integration, and human-in-the-loop approval workflows

How do I install loa-credentials?

Run the command: npx killer-skills add 0xHoneyJar/loa-freeside/loa-credentials. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

Which IDEs are compatible with loa-credentials?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add 0xHoneyJar/loa-freeside/loa-credentials. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use loa-credentials immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

loa-credentials

Multi-tenant SaaS platform for token-gated onchain communities - wallet scoring, Discord/Telegram integration, and human-in-the-loop approval workflows

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

/loa-credentials — Credential Management

Overview

Manage API credentials for Loa's multi-model provider system. Three storage tiers:

  1. Environment variables — highest priority, standard approach
  2. Encrypted store~/.loa/credentials/store.json.enc (Fernet/AES-128)
  3. .env.local — project-level dotenv file (gitignored)

Subcommands

status (default)

Show credential status for all known providers.

Workflow:

  1. Run: python3 -c "from loa_cheval.credentials import get_credential_provider; from loa_cheval.credentials.health import HEALTH_CHECKS; p = get_credential_provider('.'); [print(f'{k}: {\"configured\" if p.get(k) else \"missing\"}') for k in HEALTH_CHECKS]"
  2. Format results as a table:
    Credential Status
    ─────────────────────────────────
    OPENAI_API_KEY      configured  (env)
    ANTHROPIC_API_KEY   missing
    MOONSHOT_API_KEY    configured  (.env.local)
    
  3. If any credentials are missing, suggest: Run /loa-credentials set <NAME> to configure

set <CREDENTIAL_ID>

Store a credential in the encrypted store.

Workflow:

  1. Validate the credential ID is in the known list or matches the allowlist pattern
  2. CRITICAL: Use AskUserQuestion to prompt for the value — NEVER accept credentials as command arguments
  3. Run: python3 -c "from loa_cheval.credentials.store import EncryptedStore; s = EncryptedStore(); s.set('CREDENTIAL_ID', 'VALUE')"
  4. Confirm: "Stored CREDENTIAL_ID in encrypted store (~/.loa/credentials/)"
  5. Optionally offer to test the credential

Security Rules:

  • NEVER echo, print, or log the credential value
  • NEVER include the credential value in tool call descriptions
  • NEVER store credentials in .claude/ or grimoires/
  • The value MUST come from user input via AskUserQuestion, never from command args

test

Test all configured credentials against provider endpoints.

Workflow:

  1. Run: python3 -c "from loa_cheval.credentials import get_credential_provider; from loa_cheval.credentials.health import check_all; results = check_all(get_credential_provider('.')); [print(f'{r.credential_id}: {r.status} — {r.message}') for r in results]"
  2. Format results:
    Credential Health
    ─────────────────────────────────
    OPENAI_API_KEY      ok     — OpenAI API: valid (HTTP 200)
    ANTHROPIC_API_KEY   error  — Anthropic API: invalid key (HTTP 401)
    MOONSHOT_API_KEY    missing — MOONSHOT_API_KEY not configured
    

delete <CREDENTIAL_ID>

Remove a credential from the encrypted store.

Workflow:

  1. Confirm with user before deletion
  2. Run: python3 -c "from loa_cheval.credentials.store import EncryptedStore; s = EncryptedStore(); print('deleted' if s.delete('CREDENTIAL_ID') else 'not found')"

Error Handling

ErrorCauseResolution
"cryptography package required"Missing dependencypip install cryptography
"No credentials configured"Empty store + no env varsRun /loa-credentials set
"Health check timeout"Network issueCheck connectivity

Integration

Credentials stored via this command are automatically discovered by:

  • Config interpolation ({env:VAR} tokens in .loa.config.yaml)
  • LazyValue resolution (provider auth fields)
  • All skills that use model-invoke

The credential chain is: env var → encrypted store → .env.local Environment variables always take priority.

関連スキル

Looking for an alternative to loa-credentials or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

149.6k
0
AI

flags

Logo of vercel
vercel

React フレームワーク

138.4k
0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク(強力なGPUアクセラレーション)

98.6k
0
開発者