Registry indexed
The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate l
The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed.
Source documentation, not instructions for this website. Review permissions before running any commands.
One front door for the exo workflow lifecycle. This skill is a router. It classifies the request into one of three intents, loads the shared substrate, then loads the matching intent recipe and follows it.
Exo is an agent workflow platform. Every intent drives it through an exo MCP server.
Several exo connections coexist normally, one per workspace, sometimes several on one deployment. Enumerate the exo MCP servers this session has before doing anything else.
With exactly one, use it. With more than one, ask which through the structured question tool and stop until the user answers, because a wrong guess writes to the wrong workspace. Do not switch connections partway through an intent. Start over if the target changes.
Call whoami on the chosen server. It confirms the connection and returns the workspace ID. Report that ID so the user can see which workspace they are about to change. If no exo MCP tools are present or whoami fails, read resources/bootstrap.md and follow it, then call whoami again. Do not classify an intent until it succeeds.
scripts/exo-skill.py reaches the same workspace over REST, and it has to reach the same one. It reads EXO_API_URL, EXO_API_KEY, and EXO_WORKSPACE_ID from the process environment, falling back to the profile named by --profile, which is the file ${XDG_CONFIG_HOME:-~/.config}/exo/<name>.env. Pass --profile with the name of the MCP server you chose on every call, so the two cannot point at different workspaces.
Read resources/common.md. It holds the shared substrate every intent uses: the run-walking read primitives, the DTO discovery discipline, the resource write primitives, the unprobeable nodes, and the note on why the improve intent reads the debug recipe inline rather than invoking it.
| If the request is about | Intent | Read |
|---|---|---|
| Why a specific run failed, what went wrong with a run_id, diagnosing one run | debug | intents/debug.md |
| Improving, iterating on, tightening, or speeding up an existing workflow over its recent runs | improve | intents/improve.md |
| Turning an idea into a new workflow, building, creating, or scaffolding a workflow | build | intents/build.md |
Pick exactly one. If the request is genuinely ambiguous between intents, ask the user which one in a single question rather than guessing.
Put every question to the user through the harness's structured question tool, whatever it is called here. Free-text prose questions with bullet lists or "Q1/Q2/Q3" prompts are not allowed, even when the question feels open-ended. Bucket open areas into concrete options and let the user type a custom answer instead. Batch related questions into one call so the user answers a structured form rather than a thread of replies. Respect the current limits of the tool you have, and ask directly in prose only when no structured tool is available or the answer is inherently free-form, such as a name, a metric, or a path. This applies to intent disambiguation, the build interrogation in intents/build.md, the proposal and rerun gates in intents/improve.md, and any candidate-disambiguation prompt in intents/debug.md.
Require an explicit answer at every approval, production write, credential, and rerun gate. Never attach auto-resolution to those questions.
The boundaries between intents are intentional gates, not friction to remove. A build that ends in a first run does not auto-continue into improve, because the user owns when to cross from constructing to iterating. An improve pass that finds a failed run reads the debug walk inline rather than switching intents, because the diagnosis is a sub-procedure of the loop, not a separate request.
All paths in the intent files are relative to this skill's root directory: scripts/ for executables, resources/ for shared docs and templates, intents/ for the three recipes. agents/ holds per-harness interface metadata that no recipe reads.
name: "ghost-exo" description: The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed. license: apache-2.0 metadata: version: 1.0.0
---
name: "ghost-exo"
description: The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed.
license: apache-2.0
metadata:
version: 1.0.0
---
# exo
One front door for the exo workflow lifecycle. This skill is a router. It classifies the request into one of three intents, loads the shared substrate, then loads the matching intent recipe and follows it.
## Prerequisites
Exo is an agent workflow platform. Every intent drives it through an exo MCP server.
## Pick the connection
Several exo connections coexist normally, one per workspace, sometimes several on one deployment. Enumerate the exo MCP servers this session has before doing anything else.
With exactly one, use it. With more than one, ask which through the structured question tool and stop until the user answers, because a wrong guess writes to the wrong workspace. Do not switch connections partway through an intent. Start over if the target changes.
Call `whoami` on the chosen server. It confirms the connection and returns the workspace ID. Report that ID so the user can see which workspace they are about to change. If no exo MCP tools are present or `whoami` fails, read `resources/bootstrap.md` and follow it, then call `whoami` again. Do not classify an intent until it succeeds.
`scripts/exo-skill.py` reaches the same workspace over REST, and it has to reach the same one. It reads `EXO_API_URL`, `EXO_API_KEY`, and `EXO_WORKSPACE_ID` from the process environment, falling back to the profile named by `--profile`, which is the file `${XDG_CONFIG_HOME:-~/.config}/exo/<name>.env`. Pass `--profile` with the name of the MCP server you chose on every call, so the two cannot point at different workspaces.
## Always read first
Read `resources/common.md`. It holds the shared substrate every intent uses: the run-walking read primitives, the DTO discovery discipline, the resource write primitives, the unprobeable nodes, and the note on why the improve intent reads the debug recipe inline rather than invoking it.
## Classify the intent
| If the request is about | Intent | Read |
|---|---|---|
| Why a specific run failed, what went wrong with a run_id, diagnosing one run | debug | `intents/debug.md` |
| Improving, iterating on, tightening, or speeding up an existing workflow over its recent runs | improve | `intents/improve.md` |
| Turning an idea into a new workflow, building, creating, or scaffolding a workflow | build | `intents/build.md` |
Pick exactly one. If the request is genuinely ambiguous between intents, ask the user which one in a single question rather than guessing.
## User interaction
Put every question to the user through the harness's structured question tool, whatever it is called here. Free-text prose questions with bullet lists or "Q1/Q2/Q3" prompts are not allowed, even when the question feels open-ended. Bucket open areas into concrete options and let the user type a custom answer instead. Batch related questions into one call so the user answers a structured form rather than a thread of replies. Respect the current limits of the tool you have, and ask directly in prose only when no structured tool is available or the answer is inherently free-form, such as a name, a metric, or a path. This applies to intent disambiguation, the build interrogation in `intents/build.md`, the proposal and rerun gates in `intents/improve.md`, and any candidate-disambiguation prompt in `intents/debug.md`.
Require an explicit answer at every approval, production write, credential, and rerun gate. Never attach auto-resolution to those questions.
The boundaries between intents are intentional gates, not friction to remove. A build that ends in a first run does not auto-continue into improve, because the user owns when to cross from constructing to iterating. An improve pass that finds a failed run reads the debug walk inline rather than switching intents, because the diagnosis is a sub-procedure of the loop, not a separate request.
## Paths
All paths in the intent files are relative to this skill's root directory: `scripts/` for executables, `resources/` for shared docs and templates, `intents/` for the three recipes. `agents/` holds per-harness interface metadata that no recipe reads.
Skill source recorded
Skill instructions are recorded. This is not a runtime test, safety guarantee or compatibility certification.
Review before install: Avoid automatic install
License: apache-2.0
Install targets
Codex install prompt
Install the "ghost-exo" agent skill from https://github.com/ghostsecurity/skills/tree/main/plugins/ghost/skills/exo. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ghostsecurity-ghost-exo","task":"Install ghost-exo","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: plugins/ghost/skills/exo/SKILL.md. Recorded revision: afe9b816df6432dafb9e385dd587cb9f3f7f1a4e. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects.Repository metadata and review signals are advisory. Popularity, source discovery and successful execution are different facts.
Version reported in registry metadata; check source releases before relying on it.
Quality
73/100
Strong
Trust
69/100
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
{
"version": "openagentskill-agent-metadata-v2",
"review_evidence": {
"indexed": true,
"static_checked": false,
"ai_reviewed": false,
"manual_reviewed": false,
"creator_verified": false,
"review_result": "not_recorded",
"reviewed_at": null,
"package_fingerprint": null,
"policy_version": null,
"notice": "Publication, static checks, AI review, and creator verification are independent facts. None guarantees runtime safety."
},
"skill": {
"slug": "ghostsecurity-ghost-exo",
"name": "ghost-exo",
"description": "The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed.",
"category": "research",
"url": "https://www.openagentskill.com/skills/ghostsecurity-ghost-exo",
"repository": "https://github.com/ghostsecurity/skills/tree/main/plugins/ghost/skills/exo",
"github_repo": "ghostsecurity/skills"
},
"suited_tasks": [
"Coding agents workflows",
"Claude Code teams",
"builders willing to evaluate younger projects",
"Inspect source files",
"Explain architecture",
"Patch bugs and verify changes",
"Search sources",
"Extract claims"
],
"suited_agents": [
"Codex",
"Claude Code",
"Cursor",
"OpenAgentSkill CLI",
"CLI"
],
"install": {
"source_evidence": {
"status": "source-recorded",
"sourceRecorded": true,
"canOfferInstall": true,
"path": "plugins/ghost/skills/exo/SKILL.md",
"revision": "afe9b816df6432dafb9e385dd587cb9f3f7f1a4e",
"notice": "A skill instruction path and install command are recorded. This is not proof of compatibility, runtime success or safety; review the source and permissions first."
},
"command": "npx skills add ghostsecurity/skills --skill ghost-exo",
"ready": true,
"targets": [
{
"id": "openagentskill-cli",
"label": "CLI",
"kind": "command",
"value": "npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.3.0/openagentskill-0.3.0.tgz add ghostsecurity-ghost-exo"
},
{
"id": "codex",
"label": "Codex",
"kind": "agent-prompt",
"value": "Install the \"ghost-exo\" agent skill from https://github.com/ghostsecurity/skills/tree/main/plugins/ghost/skills/exo. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {\"event_id\":\"install_<unique-id>\",\"skill_slug\":\"ghostsecurity-ghost-exo\",\"task\":\"Install ghost-exo\",\"agent\":\"codex\",\"outcome\":\"success\",\"install_used\":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: plugins/ghost/skills/exo/SKILL.md. Recorded revision: afe9b816df6432dafb9e385dd587cb9f3f7f1a4e. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects."
},
{
"id": "claude-code",
"label": "Claude Code",
"kind": "agent-prompt",
"value": "Add \"ghost-exo\" as a Claude Code skill from https://github.com/ghostsecurity/skills/tree/main/plugins/ghost/skills/exo. Inspect the skill instructions, place the reusable skill files in the appropriate local skills location for this project, and report the activation steps. Skill purpose: The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {\"event_id\":\"install_<unique-id>\",\"skill_slug\":\"ghostsecurity-ghost-exo\",\"task\":\"Install ghost-exo\",\"agent\":\"claude-code\",\"outcome\":\"success\",\"install_used\":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: plugins/ghost/skills/exo/SKILL.md. Recorded revision: afe9b816df6432dafb9e385dd587cb9f3f7f1a4e. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects."
},
{
"id": "cursor",
"label": "Cursor",
"kind": "agent-prompt",
"value": "Turn \"ghost-exo\" from https://github.com/ghostsecurity/skills/tree/main/plugins/ghost/skills/exo into a reusable Cursor project rule or agent instruction. Preserve the core workflow, adapt paths to this repo, and keep the rule scoped to tasks where it is relevant. Skill purpose: The single interface for building, improving, and debugging exo workflows. Routes to one of three intents. BUILD takes a rough idea through interrogation, assessment, resource creation in dependency order, and one manual run, then hands off. IMPROVE runs the observe-and-iterate loop over recent runs, proposing and applying changes behind two gates. DEBUG diagnoses one failed or misbehaving run by walking the dependency graph of everything it touched. Use whenever the user wants to create a new exo workflow, iterate on or improve an existing one, or find out why a specific run failed. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {\"event_id\":\"install_<unique-id>\",\"skill_slug\":\"ghostsecurity-ghost-exo\",\"task\":\"Install ghost-exo\",\"agent\":\"cursor\",\"outcome\":\"success\",\"install_used\":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: plugins/ghost/skills/exo/SKILL.md. Recorded revision: afe9b816df6432dafb9e385dd587cb9f3f7f1a4e. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects."
}
],
"handoff_url": "https://www.openagentskill.com/api/skills/ghostsecurity-ghost-exo/install",
"manifest_url": "https://www.openagentskill.com/api/registry/manifest/ghostsecurity-ghost-exo"
},
"trust": {
"score": 77,
"label": "Strong shortlist",
"version": "trust-score-v4",
"install_policy": "review",
"evidence": {
"stars": "405 GitHub stars",
"repoActivity": "405 stars, 26 forks",
"lastPushed": "9d since push",
"license": "apache-2.0",
"repository": "https://github.com/ghostsecurity/skills/tree/main/plugins/ghost/skills/exo",
"install": "npx skills add ghostsecurity/skills --skill ghost-exo",
"installSafety": "standard package or runtime install path",
"permissionSurface": "secrets or environment access, filesystem or document access",
"documentation": "Usable metadata, review docs",
"agentOutcomes": "No agent outcome data yet"
},
"outcome_evidence": {
"total": 0,
"successes": 0,
"failures": 0,
"not_relevant": 0,
"success_rate": null,
"recent_success_rate": null,
"recent_failure_rate": null,
"install_attempts": 0,
"install_success_rate": null,
"risk_blocked": 0,
"setup_required": 0,
"avg_output_quality": null,
"production_outcomes": 0,
"last_outcome_at": null,
"label": "No agent outcome data yet"
},
"auto_install": {
"allowed": false,
"sandbox_required": true,
"reason": "Test manually in an isolated workspace and compare against safer alternatives."
},
"best_for": [
"research",
"agent-skill"
],
"known_risks": [
"Financial research output is not financial advice; require human review before any live investment decision.",
"Quality score needs review",
"Permission surface needs review: secrets or environment access, filesystem or document access",
"Stars/forks activity: 405 stars, 26 forks; issue activity unavailable in current metadata",
"Permission surface: secrets or environment access, filesystem or document access"
]
},
"agent_proven": {
"version": "agent-proven-v1",
"score": 0,
"tier": "unproven",
"label": "Needs first agent run",
"summary": "No agent outcome reports yet. Use Resolve, run one narrow sandbox task, then report the result.",
"metrics": {
"totalOutcomes": 0,
"successfulOutcomes": 0,
"failedOutcomes": 0,
"installAttempts": 0,
"installSuccessRate": null,
"successRate": null,
"recentSuccessRate": null,
"recentFailureRate": null,
"riskBlocked": 0,
"setupRequired": 0,
"notRelevant": 0,
"avgOutputQuality": null,
"avgTimeToUsefulMs": null,
"productionOutcomes": 0,
"humanReviewRequired": 0,
"uniqueAgents": 0,
"lastOutcomeAt": null
},
"signals": [],
"penalties": [
"No real agent outcome evidence yet"
]
},
"audit": {
"score": 82,
"risk_level": "needs_review",
"risk_label": "Needs review",
"warnings": [
"Permission surface may require sandboxing",
"Financial research output is not financial advice; require human review before any live investment decision",
"Financial research output is not financial advice; require human review before any live investment decision.",
"Quality score needs review",
"Permission surface needs review: secrets or environment access, filesystem or document access",
"Stars/forks activity: 405 stars, 26 forks; issue activity unavailable in current metadata",
"Permission surface: secrets or environment access, filesystem or document access"
]
},
"safety_gate": {
"tier": "experimental",
"label": "Experimental",
"auto_install_policy": "review",
"auto_install_allowed": false,
"human_review_required": true,
"blocked": false,
"recommended_action": "Test manually in an isolated workspace and compare against safer alternatives."
},
"quality": {
"score": 73,
"label": "Strong"
},
"supply": {
"track": "Research and knowledge work",
"scenario": "Research agents",
"maintenance": "9d since push",
"risk": "Needs review"
},
"alternative_skills": [
{
"slug": "mvanhorn-last30days-skill",
"name": "Last30days Skill",
"url": "https://www.openagentskill.com/skills/mvanhorn-last30days-skill",
"stars": 60956,
"install_command": "",
"trust_score": 94,
"audit_score": 95
},
{
"slug": "yanliudesign-mono-color-skill",
"name": "mono-color",
"url": "https://www.openagentskill.com/skills/yanliudesign-mono-color-skill",
"stars": 1919,
"install_command": "npx skills add yanliudesign/mono-color-skill --skill mono-color",
"trust_score": 85,
"audit_score": 93
}
],
"do_not_use_when": [
"teams that need a vendor-supported SLA",
"high-compliance environments without internal security review",
"No major risk signals from current metadata",
"High-risk permission hints: Secrets or environment access",
"Permission surface may require sandboxing",
"Financial research output is not financial advice; require human review before any live investment decision",
"Financial research output is not financial advice; require human review before any live investment decision.",
"Quality score needs review"
],
"agent_contract": {
"task_input": "Use ghost-exo in an agent workflow",
"recommended_action": "Test manually in an isolated workspace and compare against safer alternatives.",
"install_policy": "review",
"minimum_review_before_use": [
"Trust: 77/100 Strong shortlist",
"Audit: 82/100 Needs review",
"Safety: 50/100 Avoid automatic install",
"Review repository, license, install command, and permission surface before production use."
],
"expected_agent_output": {
"selected_skill": "ghostsecurity-ghost-exo (ghost-exo)",
"install_command": "npx skills add ghostsecurity/skills --skill ghost-exo",
"risk_summary": "Needs review; Experimental; Review before production",
"verification_result": "Report the smallest successful task, files touched, warnings, and any missing setup."
}
},
"outcome_feedback": {
"endpoint": "https://www.openagentskill.com/api/agent/outcome",
"method": "POST",
"requires_resolve_event_id": true,
"event_id_source": "Use install_receipt.outcome_feedback.event_id or feedback.event_id returned by /api/agent/resolve for the current task.",
"expected_outcomes": [
"success",
"failed",
"not_relevant",
"blocked_by_risk",
"setup_required"
],
"payload_template": {
"event_id": "<install_receipt.outcome_feedback.event_id or feedback.event_id from /api/agent/resolve>",
"skill_slug": "ghostsecurity-ghost-exo",
"task": "Use ghost-exo in an agent workflow",
"agent": "codex",
"outcome": "success",
"install_used": true,
"risk_blocked": false,
"setup_required": false,
"task_success": true,
"output_quality": 4,
"error_type": null,
"human_review_required": false,
"workspace": "sandbox",
"time_to_useful_ms": 120000,
"notes": "Report the smallest successful task, setup friction, files touched, and risk notes."
}
},
"endpoints": {
"web": "https://www.openagentskill.com/skills/ghostsecurity-ghost-exo",
"api": "https://www.openagentskill.com/api/agent/skills/ghostsecurity-ghost-exo",
"audit": "https://www.openagentskill.com/skills/ghostsecurity-ghost-exo/audit",
"eval": "https://www.openagentskill.com/api/agent/evals?slug=ghostsecurity-ghost-exo&task=Use%20ghost-exo%20in%20an%20agent%20workflow&max_risk=medium",
"resolve": "https://www.openagentskill.com/api/agent/resolve?task=Use%20ghost-exo%20in%20an%20agent%20workflow&agent=codex&max_risk=medium",
"receipt": "https://www.openagentskill.com/api/agent/receipt?task=Use%20ghost-exo%20in%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text",
"install": "https://www.openagentskill.com/api/skills/ghostsecurity-ghost-exo/install",
"manifest": "https://www.openagentskill.com/api/registry/manifest/ghostsecurity-ghost-exo"
}
}Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to ghostsecurity but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ghostsecurity-ghost-exo?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ghostsecurity-ghost-exo?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ghostsecurity-ghost-exo/audit)
[](https://www.openagentskill.com/skills/ghostsecurity-ghost-exo?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Listed tools are metadata hints, not tested compatibility. Agent prompts are suggested handoffs.
Check the source for dependencies, API keys and third-party costs. A public repository does not mean every service is free.
Audit
82/100
Needs review
Copies are not installs. Installation counts require a reported successful installation; they are not a blanket quality guarantee.