← Back to Skills Marketplace
athola

Nm Leyline Authentication Patterns

by athola · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
106
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install nm-leyline-authentication-patterns
Description
Authentication patterns for external services: API keys, OAuth, token management, verification. authentication, API keys, OAuth, token management, credentials.
Usage Guidance
This is a documentation-only skill that outlines patterns for API keys, OAuth, token refresh, and an interactive shell helper that caches tokens locally. Before installing or using it: 1) Understand it expects and may prompt you to enter sensitive credentials (GitHub/GitLab/AWS/GCP tokens) and will cache them under ~/.cache/claude-auth or standard CLI config paths — use ephemeral tokens where possible and inspect/delete caches after use. 2) It runs local CLIs (gh, glab, aws, gcloud and arbitrary binaries named by a 'service' parameter) — ensure those CLIs are trusted and present; malicious or misconfigured binaries with the same name could be invoked. 3) The skill references a script path to source (plugins/leyline/scripts/interactive_auth.sh) that is not included here; review or provide the actual script before sourcing. 4) In CI use secrets management (GitHub Actions secrets, etc.) rather than interactive credential entry. If you need higher assurance, ask the author for the interactive_auth.sh script and for explicit explanation of the declared config path (night-market.error-patterns) and confirm where on disk tokens are stored and how they are secured/rotated.
Capability Analysis
Type: OpenClaw Skill Name: nm-leyline-authentication-patterns Version: 1.0.0 The skill bundle provides a comprehensive set of patterns and utilities for managing authentication with external services like GitHub, GitLab, and AWS. It includes documentation and code snippets for API key verification, OAuth flows, token caching, and session management. The functionality is clearly aligned with its stated purpose of credential management, using standard CLI tools (gh, glab, aws) and local caching (e.g., ~/.cache/claude-auth), with no evidence of malicious intent or data exfiltration.
Capability Tags
requires-oauth-token
Capability Assessment
Purpose & Capability
Name/description match the content: the files document API-key, OAuth, and token flows and give shell/python patterns for verification and caching. One minor mismatch: the metadata declares a required config path (night-market.error-patterns) that is not explained in the description or modules and appears unrelated to core auth functionality.
Instruction Scope
SKILL.md and modules instruct the agent/workflow to read environment variables, prompt for secrets, run local CLIs (gh, glab, aws, gcloud, arbitrary <service> binaries via subprocess), and store tokens in ~/.cache/claude-auth/. Those behaviors are coherent for an authentication helper, but they do grant the skill the ability to run arbitrary local commands (dependent on the 'service' value) and to persist secrets to disk — both of which the user should be aware of.
Install Mechanism
Instruction-only skill with no install spec and no code files to write to disk. Low install-surface risk.
Credentials
The skill declares no required env vars but its instructions and examples read and suggest setting many sensitive environment variables (GITHUB_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, GOOGLE_APPLICATION_CREDENTIALS, etc.). This is proportionate to an auth helper, but the metadata omission (no required envs) means the skill will attempt to access secrets at runtime without having declared them up front.
Persistence & Privilege
The documentation instructs caching tokens and session files under ~/.cache/claude-auth and references token storage locations under ~/.config/{service}. This is expected for convenience but results in persistent sensitive data on disk; the skill does not request always:true and does not modify other skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install nm-leyline-authentication-patterns
  3. After installation, invoke the skill by name or use /nm-leyline-authentication-patterns
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of authentication-patterns skill, ported from claude-night-market/leyline. - Provides common authentication methods: API keys, OAuth, token management. - Includes guides for credential verification, error handling, and integration patterns. - Features sample code for smoke testing and interactive authentication workflows. - Supports multiple services with token caching and session management. - Documentation includes troubleshooting steps and resource links.
Metadata
Slug nm-leyline-authentication-patterns
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Nm Leyline Authentication Patterns?

Authentication patterns for external services: API keys, OAuth, token management, verification. authentication, API keys, OAuth, token management, credentials. It is an AI Agent Skill for Claude Code / OpenClaw, with 106 downloads so far.

How do I install Nm Leyline Authentication Patterns?

Run "/install nm-leyline-authentication-patterns" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Nm Leyline Authentication Patterns free?

Yes, Nm Leyline Authentication Patterns is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Nm Leyline Authentication Patterns support?

Nm Leyline Authentication Patterns is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Nm Leyline Authentication Patterns?

It is built and maintained by athola (@athola); the current version is v1.0.0.

💬 Comments