What makes lingry notable?

969 downloads. Trust evidence available

How should lingry be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

lingry

Discover Lingry words, generate immutable candidates, and coin only the currently selected candidate after explicit user publication intent.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

969

Updated

Oct 12, 2026

Version

2.0.9

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 969 downloads reported by the source. Last updated 10/12/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 12, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 12, 2026
Adoption signal: 969 downloadsadoption · observed Oct 12, 2026
Latest release: 2.0.9release · observed Sep 25, 2026
Handshake status: UNKNOWNsecurity

What changed

Newest first. Only changes that point at a source are listed.

Release 2.0.9release
- No user-facing changes or code updates in this release. - Version bump only; functionality and instructions remain unchanged.
Observed Sep 25, 2026 · source

Install and run

Setup complexity: low.

clawhub skill install s17c2gj8xwmebbz5gby98gdmqs89f7eb:lingry

Install using `clawhub skill install s17c2gj8xwmebbz5gby98gdmqs89f7eb:lingry` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/svetlyoh/lingry before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-svetlyoh-lingry/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

151,423 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: lingry
description: Discover Lingry words, generate immutable candidates, and coin only the currently selected candidate after explicit user publication intent.
version: 2.1.0
homepage: https://github.com/svetlyoh/web-wallet/tree/master/skills/lingry
metadata:
openclaw:
requires:
bins:
- node
homepage: https://github.com/svetlyoh/web-wallet/tree/master/skills/lingry
---

# Lingry agent skill

Use Lingry to discover public words and generate candidate terms. At runtime, the skill calls only `https://lingry.net`. It stores no local state or credential and uses no wallet or signing key. The default language code is `W` (American English); use `--language=<code>` when the user requests another Lingry language. `E` means British English. Do not silently force a locale variant.

## Install

Lingry is a multi-file Node.js skill. `SKILL.md` alone is not an installation: obtain the complete directory, including `bin/`, `src/`, `package.json`, `INSTALL.json`, and `CHANGELOG.md`. Node.js >= 18 is required. No `npm install`, OpenClaw installation, wallet setup, or local secret is required for Muse or other agents.

### OpenClaw

From the OpenClaw workspace, use the ClawHub package:

```bash
cd ~/.openclaw/workspace
openclaw skills install '@svetlyoh/lingry'
```

### Muse Code

Open the ClawHub [Versions tab](https://clawhub.ai/svetlyoh/skills/lingry#versions), select **Download** beside the latest version, and extract the downloaded package. Use the resulting `lingry` directory—the folder that directly contains `SKILL.md`, `README.md`, `CHANGELOG.md`, `INSTALL.json`, `package.json`, `bin/`, and `src/`. Muse loads the skill instructions; the agent uses its normal tools to run Lingry's Node commands. It does not need OpenClaw.

```bash
muse skills validate /path/to/lingry
muse skills install /path/to/lingry --scope user --name lingry
cd /path/to/lingry
node bin/lingry-agent.mjs verify-install
```

### Other SKILL.md-compatible agents

Open the ClawHub [Versions tab](https://clawhub.ai/svetlyoh/skills/lingry#versions), select **Download** beside the latest version, and extract the downloaded package. Place the resulting `lingry` directory in your agent's documented skills location. If it supports the cross-agent convention, `~/.agents/skills/lingry/` is an option; do not assume every agent scans it. Confirm the installed folder has `SKILL.md`, `README.md`, `CHANGELOG.md`, `INSTALL.json`, `package.json`, `bin/`, and `src/`, then run `node bin/lingry-agent.mjs verify-install` from that folder. An agent may instead use an absolute path to `bin/lingry-agent.mjs`.

### Optional GitHub fallback

If the agent cannot download the complete package from ClawHub, use Git sparse checkout (or equivalent PowerShell commands on Windows) to obtain the clean seven-file package:

```bash
git clone --filter=blob:none --no-checkout https://github.com/svetlyoh/web-wallet.git lingry-source
cd lingry-source
git sparse-checkout init --cone
git sparse-

README.md

# Lingry agent skill

The skill discovers public Lingry words, requests a server-generated word candidate, and publishes only the selected immutable candidate after an explicit user request. The service origin is fixed at `https://lingry.net`.

## Install

`openclaw/skills/lingry/` is the canonical source directory. The clean GitHub-import folder for ClawHub is [`skills/lingry/`](https://github.com/svetlyoh/web-wallet/tree/master/skills/lingry); it mirrors the staged release, without development files. The skill is multi-file: `SKILL.md` alone cannot run it. Node.js >= 18 is required; there are no npm runtime dependencies, so no `npm install` is needed. The version source of truth is the source directory's `package.json`.

### OpenClaw

```bash
cd ~/.openclaw/workspace
openclaw skills install '@svetlyoh/lingry'
```

### Muse Code

Open the ClawHub [Versions tab](https://clawhub.ai/svetlyoh/skills/lingry#versions), select **Download** beside the latest version, and extract the downloaded package. Use the resulting `lingry` directory—the folder that directly contains `SKILL.md`, `README.md`, `CHANGELOG.md`, `INSTALL.json`, `package.json`, `bin/`, and `src/`:

```bash
muse skills validate /path/to/lingry
muse skills install /path/to/lingry --scope user --name lingry
cd /path/to/lingry
node bin/lingry-agent.mjs verify-install
```

Muse loads the instructions; its agent runs the Node CLI through normal tools. OpenClaw is not required.

### Other agents

Open the ClawHub [Versions tab](https://clawhub.ai/svetlyoh/skills/lingry#versions), select **Download** beside the latest version, and extract the package. Place the resulting `lingry` directory in your agent's supported skills directory. `~/.agents/skills/lingry/` is one option for agents that support the cross-agent convention. Run `node bin/lingry-agent.mjs verify-install` from the installed directory.

### Optional GitHub fallback

If the agent cannot download the complete package from ClawHub, use Git sparse checkout to obtain the clean seven-file package:

```bash
git clone --filter=blob:none --no-checkout https://github.com/svetlyoh/web-wallet.git lingry-source
cd lingry-source
git sparse-checkout init --cone
git sparse-checkout set skills/lingry
git checkout
cd skills/lingry
node bin/lingry-agent.mjs verify-install
```

From the checkout, copy `skills/lingry/` to the agent's documented skills location if needed. On Windows, use the equivalent PowerShell copy commands.

## Workflow

Use `generate-word "a concept"` to obtain an immutable candidate. Show the term, meaning, part of speech, and language. Then offer **Coin this term** and **Prompt for another**. `prompt-another "new concept"` only generates a new candidate. To publish, the user must explicitly request coining of the currently displayed candidate; the agent then uses `coin-word <candidate-id> --publish`. The server returns a transaction ID after publication. Retry with the same ID is idempotent.

`W` is Lingry's American English code

_meta.json

{
  "ownerId": "kn74nezws67n3b8keq4safmb7x89e5v1",
  "slug": "lingry",
  "version": "2.0.9",
  "publishedAt": 1790356737034
}

CHANGELOG.md

# Changelog

## 2.1.0

- Made ClawHub the primary installation source for Muse and other compatible agents, with Git sparse checkout retained only as an optional fallback.
- Linked Muse and generic-agent instructions directly to ClawHub's Versions tab so users can select the latest downloadable package.
- Included this changelog in the published ClawHub package.
- Removed local publisher credentials, candidate files, state-path and API-origin overrides from the ClawHub client.
- Added server-generated, expiring candidate capabilities and a candidate-only publication endpoint.
- Replaced executable next-action strings with structured intents and strict candidate ID validation.
- Added a minimal ClawHub staging build that excludes tests and development files.
- Added portable Muse/generic-agent install instructions, Git sparse checkout, and read-only local verification.
- Added deterministic ZIP, SHA256 and file manifests from the same staged ClawHub payload, plus a deliberate GitHub Release workflow.

## 2.0.2

- Added two explicit actions after every generated candidate: coin this term or prompt for another.
- Kept both the current and replacement candidate uncoined until the user explicitly requests publication.

## 2.0.1

- Documented the exact workspace-scoped, quoted ClawHub install command shown to users.
- Removed unnecessary post-install `npm` and manual verification steps.
- Confirmed clean-install word generation automatically creates the workspace credential, bootstraps the Agent Publisher, and opens a short-lived session without user-provided keys or secrets.
- Clarified that publisher-key encryption is server-managed and operator configuration errors are not transient client failures.

## 2.0.0

- Removed the OpenClaw local Sugarchain wallet, private-key import, browser API Session copy/paste, and manual transaction approval workflow.
- Added automatic workspace-scoped Agent Publisher registration and short-lived session renewal.
- Added one unique Lingry-managed Sugarchain publishing address per OpenClaw agent workspace.
- Added autonomous, policy-constrained coining of immutable canonical Lingry candidates.
- Added first-use public Stream onboarding and read-only Daily Lingry Word automation guidance.

## 1.0.7

- Change default public leaderboard and stream command limits to 100 records.

## 1.0.6

- Accept direct public snapshot responses for leaderboard and stream commands.

## 1.0.5

- Added public hourly-indexed leaderboard and stream commands for OpenClaw.

## 1.0.4

- Clarify first-run setup: create or open a `lingry.net` wallet first, import the matching private/login key on Ubuntu OpenClaw, then configure the 30-day API session token.
- Add stale OpenClaw gateway environment troubleshooting for cases where terminal `auth-status` accepts a new token but chat still reports an old expiry.

## 1.0.3

- Add first-launch OpenClaw setup instructions for ownership repair, wallet import, session-token storage, gateway restart, and t

skill-card.md

## Description:

Discover Lingry words, generate immutable candidates, and coin only the currently selected candidate after explicit user publication intent.

This skill is ready for commercial/non-commercial use.

## Publisher:

[svetlyoh](https://clawhub.ai/user/svetlyoh)

### License/Terms of Use:

MIT-0

## Use Case:

People using an agent can discover public Lingry words, generate candidates from concepts, and explicitly publish a selected candidate.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Word prompts are sent to Lingry's server.

Mitigation: Share only concepts you are comfortable sending to the service; never provide wallet secrets.

Risk: Coining permanently publishes the selected candidate.

Mitigation: Coin only after the user explicitly requests publication of the currently selected candidate.

## Reference(s):

- [Lingry project homepage](https://github.com/svetlyoh/web-wallet/tree/master/skills/lingry)
- [Lingry service](https://lingry.net)
- [ClawHub Lingry release](https://clawhub.ai/svetlyoh/skills/lingry)

## Skill Output:

**Output Type(s):** [Text, Guidance]

**Output Format:** [Markdown with word and candidate details]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [A published candidate returns a transaction ID; generating a candidate does not publish it.]

## Skill Version(s):

2.0.9 (source: ClawHub release metadata; bundled files declare 2.1.0)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 3d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW

Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular