Skills integration-tests

📦

integration-tests

Name: integration-tests
Author: internet-court

Content revision r1 Safe ⚙️ External commands🔑 Env variables

Run GenLayer Integration Tests

GenLayer contract teams need tests that match real consensus behavior. This skill shows gltest patterns, environment choices, and safety checks for reliable integration testing.

Supports: Claude Codex Code(CC)

🥉 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 "integration-tests" from https://skillstore.io/skills/internet-court-integration-tests.md and its manifest at https://skillstore.io/api/skills/internet-court-integration-tests/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.

Markdown detail GET /skills/internet-court-integration-tests.md Signed manifest GET /api/skills/internet-court-integration-tests/manifest Signed lockfile GET /api/skills/internet-court-integration-tests/lockfile

Test it

Using "integration-tests". Add integration tests for a storage contract.

Expected outcome:

A recommended environment for fast iteration and final validation.
A test flow that deploys the contract, writes data, checks receipt success, and verifies stored values.
A note to use direct mode for most pure logic tests.

Using "integration-tests". Explain why my finalized transaction changed no state.

Expected outcome:

A distinction between lifecycle status and execution success.
A reminder to assert receipt success before reading state.
Likely causes for missing contracts after failed deployments.

Using "integration-tests". Prepare my suite for hosted Studio.

Expected outcome:

A checklist for rate limits, pending transaction caps, and pacing.
Advice to run heavy batches on localnet instead.
A warning that integration tests may make real web or LLM calls.

Security Audit

Safe

v2 • 7/21/2026 Open versioned report

All 25 external-command findings are false positives caused by Markdown fences and inline code formatting in SKILL.md. The two private-key findings document environment-variable configuration for testnet accounts and show no secret access or exfiltration. No prompt injection, malicious intent, or additional semantic security issue was found.

Files scanned

152

Lines analyzed

Review items

False positives ignored

Risk Factors

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: claude 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

Copy report link

https://skillstore.io/skills/internet-court-integration-tests/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/internet-court-integration-tests/security.svg)](https://skillstore.io/skills/internet-court-integration-tests?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/internet-court-integration-tests?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-integration-tests/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-integration-tests.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

internet-court. (2026). integration-tests security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/internet-court-integration-tests/audits/2

BibTeX citation

@techreport{internet-court-internet-court-integration-tests-2026,
  author = {internet-court},
  title = {integration-tests security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/internet-court-integration-tests/audits/2},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "integration-tests security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
  - name: "internet-court"
date-released: "2026-07-21"
url: "https://skillstore.io/skills/internet-court-integration-tests/audits/2"
identifiers:
  - type: other
    value: "skillstore:internet-court-integration-tests:audit:2"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Validate Contract Consensus

Check that leader and validators agree before deployment.

Build Release Smoke Tests

Create integration checks that deploy, transact, and verify state.

Choose Test Environments

Select GLSim, local Studio, hosted Studio, or testnet for each test goal.

Try These Prompts

Create a Basic Test

Add a basic GenLayer integration test with deploy, transact, receipt assertion, and read checks.

Pick the Right Environment

Recommend a GenLayer test environment for this suite and explain the setup, speed, and validation tradeoffs.

Debug a Failing Run

Diagnose this failed gltest run and suggest fixes for receipts, cache state, serialization, or rate limits.

Prepare for Testnet

Review this suite for testnet readiness, including private-key handling, funded accounts, rate limits, and pending transactions.

Best Practices

Assert transaction execution success before reading state or checking contract results.
Use direct mode for most logic tests and integration tests for final validation.
Run heavy batches against GLSim or local Studio before hosted Studio or testnet.

Avoid

Treating accepted or finalized status as proof of successful execution.
Submitting many transactions in parallel from the same sender.
Using funded private keys without explicit user approval and secret handling.

Frequently Asked Questions

What does this skill help test?

It helps test GenLayer contracts against consensus environments, including GLSim, Studio, and testnet.

Does it replace direct mode tests?

No. Direct mode should cover most logic tests. Integration tests validate final runtime behavior.

Can it use Claude, Codex, and Claude Code?

Yes. The report declares support for Claude, Codex, and Claude Code.

Does hosted Studio require tokens?

The skill says StudioNet is gasless, but hosted rate limits still apply.

Why check transaction receipts?

Accepted and finalized states do not prove execution success or state changes.

What secrets need extra care?

Private keys for funded testnet accounts need strict environment and logging controls.

Developer Details

Author

internet-court

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/internet-court/internet-court-skill/tree/main/vendored/genlayer/integration-tests

Ref

3f6e026a3363e0954ede7bef0cfe88d4475de137

Maintenance freshness

7/21/2026

Usage

1 downloads · 0 views

File structure

📁 agents/

📄 openai.yaml

📄 SKILL.md