Skills sail-verification
๐Ÿ“ฆ

sail-verification

v1.0.0 Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access

Verify Rust Proofs and SMT Queries with Sail

Repeated Verus checks and SMT queries can slow proof development and complicate evidence tracking. This skill guides Sail workflows for cached verification, repair validation, and accurate result interpretation.

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it ๐Ÿฅ‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "sail-verification" from https://skillstore.io/skills/chelis-lang-sail-verification.md and its manifest at https://skillstore.io/api/skills/chelis-lang-sail-verification/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "sail-verification". Illustrate a report for a focused proof check that passes without full-target evidence.

Expected outcome:

The selected function passed. Full-target verification has not completed, so the repair remains provisional.

Using "sail-verification". Illustrate a result summary for a cached SMT query requiring an integer greater than two.

Expected outcome:

The formula is satisfiable. The returned model assigns an integer greater than two. The result reports a cache hit for this matching request.

Using "sail-verification". Illustrate a report when successful verification predates source changes.

Expected outcome:

The earlier result was successful but is now Historical. Verify the current inputs again before reporting a current proof.

Security Audit

Safe
v2 โ€ข 11/4/2026 Open versioned report

All nine static findings are false positives: seven match Markdown backticks, and two identify documentation links without data transmission instructions. No evidence found of prompt injection, credential collection, or exfiltration in the reviewed skill files. The documented commands support local verification and solver workflows, but the external Sail implementation was not audited.

4
Files scanned
286
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/chelis-lang-sail-verification/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/chelis-lang-sail-verification/security.svg)](https://skillstore.io/skills/chelis-lang-sail-verification?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/chelis-lang-sail-verification?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chelis-lang-sail-verification/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/chelis-lang-sail-verification.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

chelis-lang. (2026). sail-verification security audit report (audit version 2) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/chelis-lang-sail-verification/audits/2

BibTeX citation

@techreport{chelis-lang-chelis-lang-sail-verification-2026, author = {chelis-lang}, title = {sail-verification security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/chelis-lang-sail-verification/audits/2}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "sail-verification security audit report (audit version 2)" version: "1.0.0" type: report authors: - name: "chelis-lang" date-released: "2026-11-04" url: "https://skillstore.io/skills/chelis-lang-sail-verification/audits/2" identifiers: - type: other value: "skillstore:chelis-lang-sail-verification:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
41
Architecture
100
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

Iterate on Rust contracts

Use Sail diagnostics and reusable solver work while developing Verus proofs without weakening intended contracts.

Validate automated proof repairs

Check candidate repairs, inspect completed jobs, and require current full-target success before accepting changes.

Repeat constraint checks

Submit complete SMT-LIB transcripts, inspect models or unsat cores, and reuse matching decided results.

Try These Prompts

Verify an existing project
Use Sail to verify this Cargo/Verus project. Report the verdict, checked scope, freshness, and failure diagnostics.
Run an SMT query
Check Sail runtime capabilities, then run my SMT-LIB transcript. Report each satisfiability result, requested model or core, and cache reuse.
Check a candidate proof repair
Validate my candidate repair for [package] and [function] with Sail. Preserve the contract and require current full-target success before accepting it.
Track background verification
Use the configured Sail MCP server to submit background verification for [project]. Inspect installed schemas, read the completed result, and report scope and freshness.

Best Practices

  • Check installed help, MCP schemas, and release compatibility before choosing a workflow.
  • Require the correct scope, a successful verdict, and Current evidence before accepting verification.
  • Keep logs and transcripts outside watched inputs, and preserve intended contracts during repairs.

Avoid

  • Accepting a focused function pass as proof that the entire target verifies.
  • Treating runtime readiness, Unknown results, or timeouts as successful solver evidence.
  • Weakening contracts to hide implementation failures.

Frequently Asked Questions

Which systems does Sail support?
The skill documents Linux x86-64 and Apple-silicon macOS.
Does this skill include Sail, Verus, or Z3?
No. It provides workflow guidance. Sail must be installed separately and ships its own Verus and Z3.
Can I use an existing Verus project?
Yes. Sail accepts Cargo Verus verification arguments. Check compatibility and use Cargo directly when your project requires a different Verus release.
Does Current mean verification succeeded?
No. Current describes evidence freshness. Read the verdict and checked scope separately.
When can SMT output be reused?
Sail reuses decided output when transcript bytes, limits, pinned solver identity, and execution settings match. Incomplete runs are not successful evidence.
Can I use Sail through MCP?
Yes, with a configured Sail MCP server. Inspect installed tool schemas and read completed job results before reporting success.

Developer Details

License

MIT

Author version

v1.0.0

Skillstore revision

r2

Version notice

The installable content changed, but the author did not update the declared version.

Ref

1560e56cb7d29b28375339f36876381de0b278b2

Maintenance freshness

11/5/2026

Usage

1 downloads ยท 0 views

File structure

๐Ÿ“„ LICENSE

๐Ÿ“ references/

๐Ÿ“„ smt.md

๐Ÿ“„ verus.md

๐Ÿ“„ SKILL.md

View all