← Back to Skills Marketplace
clarityprotocol

Clarity Submit

by clarityprotocol · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
331
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install clarity-submit
Description
Submit a protein variant hypothesis to Clarity Protocol for validation and folding. Use when the user asks to submit a hypothesis, propose a protein variant,...
README (SKILL.md)

Clarity Submit Skill

Submit protein variant hypotheses to Clarity Protocol for automated validation and ColabFold structural prediction.

Quick Start

Submit a hypothesis:

python scripts/submit_hypothesis.py --protein SOD1 --variant A4V --rationale "ALS-linked mutation with unknown structural impact"

Submit with optional fields:

python scripts/submit_hypothesis.py --protein MAPT --variant P301L --rationale "Tau pathology in frontotemporal dementia" --wallet "YOUR_SOLANA_WALLET"

Check hypothesis status:

python scripts/check_status.py --id 42

Setup

Set your write API key:

export CLARITY_WRITE_KEY=your_write_key_here

Contact the Clarity Protocol team to request a write API key.

What Happens After Submission

  1. Feasibility validation runs automatically against UniProt, ClinVar, gnomAD, and PubMed
  2. If validated, the hypothesis is auto-queued for ColabFold structural prediction
  3. Four AI research agents continuously monitor the variant for new findings
  4. Results are available at the tracking URL returned after submission

Request Fields

  • --protein (required): Protein name (e.g., SOD1, MAPT, APP, SNCA)
  • --variant (required): Variant notation (e.g., A4V, P301L, G2019S)
  • --rationale (required): Why this variant is worth investigating (min 10 characters)
  • --disease (optional): Disease area (auto-detected from protein if omitted)
  • --wallet (optional): Solana wallet address for $FOLD reward eligibility

Response Fields

  • id: Unique hypothesis identifier
  • protein_name: Normalized protein name
  • variant_notation: Variant as submitted
  • status: Current status (submitted, validating, validated, queued, folding, complete, rejected)
  • tracking_url: URL to track progress on clarityprotocol.io

Rate Limits

  • Write (POST): 10 submissions per day per key
  • Read (GET): 100 requests per minute per key

Size Limits

Proteins up to 1,500 residues can be folded. Larger proteins (e.g., LRRK2 at 2,527 residues) exceed hardware capacity and will be rejected during validation.

Error Handling

403 Forbidden: Invalid or missing write API key. Set CLARITY_WRITE_KEY env var.

422 Validation Error: Invalid input (protein name empty, rationale too short, etc.).

429 Rate Limit: You've exceeded 10 submissions/day. Wait until tomorrow.

Use Cases

  • Programmatically submit variants for investigation
  • Integrate Clarity Protocol into research pipelines
  • Batch submission of variants of interest
  • Agent-driven hypothesis generation and submission
Usage Guidance
The code does what the description says (submits variants to clarityprotocol.io and checks status), but the registry metadata is inconsistent: it does not declare the CLARITY_WRITE_KEY/CLARITY_API_KEY env vars or a homepage/source. Before installing or running: 1) Verify the skill's origin (confirm the owner and a legitimate homepage/repo for clarityprotocol.io); 2) Only provide a write key that is scoped and revocable (do not use high-privilege or long-lived secrets); 3) Prefer testing read-only operations first (no write key) and inspect network traffic if possible; 4) If you plan to run submit_hypothesis.py, confirm the tracking URL and endpoints match the official service and that you're comfortable sending variant data to that external service. If the registry owner cannot explain the metadata omissions, treat the skill with caution.
Capability Analysis
Type: OpenClaw Skill Name: clarity-submit Version: 1.0.0 The OpenClaw skill bundle is benign. All code and documentation align with the stated purpose of interacting with the Clarity Protocol API to submit and check protein variant hypotheses. Network calls are exclusively directed to `https://clarityprotocol.io`. Environment variables (`CLARITY_WRITE_KEY`, `CLARITY_API_KEY`) are accessed securely for API authentication, not for exfiltration. The `SKILL.md` file contains no prompt injection attempts or instructions for the agent to perform actions outside its described functionality. No evidence of arbitrary command execution, sensitive file access, or obfuscation was found across `scripts/api_client.py`, `scripts/check_status.py`, and `scripts/submit_hypothesis.py`.
Capability Assessment
Purpose & Capability
The name, SKILL.md, and included scripts all align: they submit hypotheses and check status on clarityprotocol.io. However the registry metadata (no homepage, no required env vars, no primary credential) contradicts SKILL.md and the code which clearly requires CLARITY_WRITE_KEY for POSTs and optionally CLARITY_API_KEY for reads.
Instruction Scope
Runtime instructions and scripts limit operations to clarityprotocol.io endpoints and the declared submission/checking flows (POST /hypotheses, GET /lab/api/hypothesis/{id}). The SKILL.md asks the user to set CLARITY_WRITE_KEY for write operations and the scripts do not attempt to read unrelated filesystem paths or other environment variables.
Install Mechanism
This is an instruction-only skill with Python scripts and no install spec; nothing is downloaded or written to disk by an installer. Risk is limited to running the included scripts locally.
Credentials
The code requires CLARITY_WRITE_KEY (and optionally CLARITY_API_KEY) but the skill registry entry lists no required env vars or primary credential. The write key requirement is reasonable for a write operation, but the manifest omission is a coherence issue and should be corrected/clarified before trusting the skill. Ensure the write key provided has appropriate, limited scope.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide configs, and does not persist credentials itself. It runs network calls only to clarityprotocol.io.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install clarity-submit
  3. After installation, invoke the skill by name or use /clarity-submit
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the Clarity Submit skill. - Submit protein variant hypotheses to Clarity Protocol for automated validation and structural prediction. - Supports checking submission status via unique ID. - Requires the CLARITY_WRITE_KEY environment variable for write access. - Enforces write/read rate limits and protein size limits. - Provides clear error codes for invalid input, authentication failure, and rate limiting. - Enables integration into research pipelines and supports programmatic or agent-driven submissions.
Metadata
Slug clarity-submit
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Clarity Submit?

Submit a protein variant hypothesis to Clarity Protocol for validation and folding. Use when the user asks to submit a hypothesis, propose a protein variant,... It is an AI Agent Skill for Claude Code / OpenClaw, with 331 downloads so far.

How do I install Clarity Submit?

Run "/install clarity-submit" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Clarity Submit free?

Yes, Clarity Submit is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Clarity Submit support?

Clarity Submit is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Clarity Submit?

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

💬 Comments