status

Generates a diagnostic report of Seal Harness installation, project setup, and configuration issues.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/seal-harness/seal-harness --skill status-seal-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/seal-harness/seal-harness/tree/main/.agents/skills/status
Command: npx skills add https://github.com/seal-harness/seal-harness --skill status-seal-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with Seal Harness across Claude Code, Codex, Gemini, or OpenCode, it is hard to know whether the plugin is installed correctly, the project is configured, and required tools are available. This Skill runs a full diagnostic sweep and reports installation state, setup gaps, and potential conflicts in one formatted report. ## Core Features & Use Cases - Platform Detection: Automatically detects whether the active environment is Codex, Claude Code, or Gemini and adapts its checks accordingly. - Installation & Setup Checks: Verifies plugin version, project profile configuration, platform install state, command shims, and legacy embedded plugin conflicts. - Tooling & Environment Audit: Checks for the gtg CLI, external tool adapters, coverage thresholds, and Node.js availability. - Use Case: After migrating from an embedded plugin to a marketplace install, run the status check to confirm the legacy plugin is gone, the marketplace plugin is enabled, and no configuration conflicts remain. ## Quick Start Ask the agent to run the status check and show a diagnostic report of the current Seal Harness installation and project setup.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my Seal Harness plugin is installed correctly?

Run the status check, which reads the plugin manifest for your platform (.codex-plugin/plugin.json, .claude-plugin/plugin.json, or gemini-extension.json) and reports the version plus install state. It also scans the platform plugin cache to confirm marketplace installation.

How do I verify project setup after installing an agent plugin?

The status report checks for docs/project-profile.json in the working directory and reports key fields like distribution, language, framework, and test runner. If the file is missing, it tells you to run the setup command for your platform.

Does the status check work with both Claude Code and Codex?

Yes, the diagnostic detects the active platform automatically using environment variables and manifest files, then runs platform-appropriate checks. For Codex it skips Claude command shim checks, and for Claude it validates the .claude/commands/ shim files.

Why does the status report flag a legacy embedded plugin conflict?

The check looks for .claude/plugins/Seal Harness/.claude-plugin/plugin.json, which indicates an old embedded installation. If it exists alongside the marketplace plugin, the report flags it prominently and recommends running the migrate command to resolve the conflict.

What happens if a diagnostic check fails during the status report?

The status skill is diagnostic-only and never fails fatally. If an individual check errors, such as an unreadable plugin.json, it reports that specific failure inline and continues with all remaining checks.