Source profileQuality 72/100Review permissions

yun520-1/mark-heartflow-skill/skills/nexus-error-explain/SKILL.md

nexus-error-explain

Explain error messages and suggest fixes

Source repository stars: 36
Declared platforms: 0
Static risk flags: 2
Last source update: 2026-07-28
Source checked: 2026-07-28

Decision Compatibility Install Workflow Permissions Evidence Source

Decision brief

What it does—and where it fits

NEXUS Agent-as-a-Service on Cardano + Stellar + XRPL | Price: $0.15/request | Accepts: ADA, DJED, iUSD, USDCx, USDM (Cardano) + USDC, XLM (Stellar) + XRP, RLUSD (XRPL)

Best for

Use when you need to explain error messages and suggest fixes.

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/yun520-1/mark-heartflow-skill --skill "skills/nexus-error-explain"

Safe inspection promptEditorial

Inspect the Agent Skill "nexus-error-explain" from https://github.com/yun520-1/mark-heartflow-skill/blob/20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c/skills/nexus-error-explain/SKILL.md at commit 20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
When to use
Use when you need to explain error messages and suggest fixes.
Use when you need to explain error messages and suggest fixes.
02
Steps
1. Call the service endpoint without payment headers. 2. Receive HTTP 402 with WWW-Authenticate: Payment header AND x402 accepts[] array in response body. 3. Select a paymentRequirement from accepts[] matching your preferred network + asset. 4. Networks: cardano:mainnet (ADA, DJ…
Call the service endpoint without payment headers.Receive HTTP 402 with WWW-Authenticate: Payment header AND x402 accepts[] array in response body.Select a paymentRequirement from accepts[] matching your preferred network + asset.
03
Option A: x402 Standard (Recommended)
1. Call the service endpoint without payment headers. 2. Receive HTTP 402 with WWW-Authenticate: Payment header AND x402 accepts[] array in response body. 3. Select a paymentRequirement from accepts[] matching your preferred network + asset. 4. Networks: cardano:mainnet (ADA, DJ…
Call the service endpoint without payment headers.Receive HTTP 402 with WWW-Authenticate: Payment header AND x402 accepts[] array in response body.Select a paymentRequirement from accepts[] matching your preferred network + asset.
04
Option B: MPP Standard
1. Call the service endpoint without payment headers. 2. Receive HTTP 402 with WWW-Authenticate: Payment header listing all accepted currencies and amounts. 3. Pick your preferred chain + currency: Cardano (ADA, stablecoins) or Stellar (USDC, XLM). 4. Create payment: Masumi escr…
Call the service endpoint without payment headers.Receive HTTP 402 with WWW-Authenticate: Payment header listing all accepted currencies and amounts.Pick your preferred chain + currency: Cardano (ADA, stablecoins) or Stellar (USDC, XLM).
05
Option C: Legacy Header
1. Send a POST request to the NEXUS API endpoint with your input. 2. Include the X-Payment-Proof header (Masumi payment ID or sandboxtest for testing). 3. Parse the JSON response and return the result.
Send a POST request to the NEXUS API endpoint with your input.Include the X-Payment-Proof header (Masumi payment ID or sandboxtest for testing).Parse the JSON response and return the result.

Permission review

Static risk signals and limitations

Network access

medium · line 34

The documentation includes network, browsing, or remote request actions.

Send a POST request to the NEXUS API endpoint with your input.

Sends data out

high · line 41

The documentation includes sending, uploading, or posting data to a remote service.

curl -X POST https://ai-service-hub-15.emergent.host/api/original-services/error-explain \

Network access

medium · line 41

The documentation includes network, browsing, or remote request actions.

curl -X POST https://ai-service-hub-15.emergent.host/api/original-services/error-explain \

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	72/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	36	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: yun520-1/mark-heartflow-skill
Skill path: skills/nexus-error-explain/SKILL.md
Commit: 20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c
License: Not declared
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

Error Explainer

NEXUS Agent-as-a-Service on Cardano + Stellar + XRPL | Price: $0.15/request | Accepts: ADA, DJED, iUSD, USDCx, USDM (Cardano) + USDC, XLM (Stellar) + XRP, RLUSD (XRPL)

When to use

Use when you need to explain error messages and suggest fixes.

Steps

Option A: x402 Standard (Recommended)

Call the service endpoint without payment headers.
Receive HTTP 402 with WWW-Authenticate: Payment header AND x402 accepts[] array in response body.
Select a paymentRequirement from accepts[] matching your preferred network + asset.
Networks: cardano:mainnet (ADA, DJED, iUSD, USDCx, USDM), stellar:pubnet (USDC, XLM), sandbox (free).
Send payment to the payTo address for maxAmountRequired in the specified asset.
Stellar fee sponsorship: POST your signed XDR to https://ai-service-hub-15.emergent.host/api/mpp/stellar/sponsor — NEXUS pays gas, you need 0 XLM.
Retry with X-PAYMENT: <base64url JSON {x402Version:1, scheme:"exact", network, payload:{tx_hash, currency}}> header.
Parse the JSON response and X-PAYMENT-RESPONSE header.

Option B: MPP Standard

Call the service endpoint without payment headers.
Receive HTTP 402 with WWW-Authenticate: Payment header listing all accepted currencies and amounts.
Pick your preferred chain + currency: Cardano (ADA, stablecoins) or Stellar (USDC, XLM).
Create payment: Masumi escrow (Cardano) or direct Stellar transfer.
Stellar fee sponsorship: POST your signed XDR to https://ai-service-hub-15.emergent.host/api/mpp/stellar/sponsor — NEXUS pays gas, you need 0 XLM.
Retry with Authorization: Payment <base64url-credential> header.
Parse the JSON response and Payment-Receipt header.

Option C: Legacy Header

Send a POST request to the NEXUS API endpoint with your input.
Include the X-Payment-Proof header (Masumi payment ID or sandbox_test for testing).
Parse the JSON response and return the result.

API Call

curl -X POST https://ai-service-hub-15.emergent.host/api/original-services/error-explain \
  -H "Content-Type: application/json" \
  -H "X-Payment-Proof: $NEXUS_PAYMENT_PROOF" \
  -d '{
  "input": "Example input for Error Explainer"
}'

Endpoint: https://ai-service-hub-15.emergent.host/api/original-services/error-explain Method: POST Headers:

Content-Type: application/json
X-PAYMENT: <base64url JSON> (x402 standard — recommended)
Authorization: Payment <credential> (MPP standard)
X-Payment-Proof: <masumi_payment_id> (legacy — use sandbox_test for free testing)

Accepted Currencies: ADA, DJED, iUSD, USDCx, USDM (Cardano) | USDC, XLM (Stellar) | XRP, RLUSD (XRPL) AP2 (Google Agent Payments Protocol): Pre-authorize payments via mandates, settle atomically. See https://ai-service-hub-15.emergent.host/api/ap2/config. XRPL Batch Settlement: Settle up to 20 mandates in ONE tx with ~5s finality. See skill nexus-ap2-batched-settle. x402 Discovery: GET https://ai-service-hub-15.emergent.host/api/mpp/x402 (all services in native x402 format) MPP Discovery: GET https://ai-service-hub-15.emergent.host/api/mpp/discover Stablecoin Registry: GET https://ai-service-hub-15.emergent.host/api/mpp/stablecoins (includes on-chain policy IDs) Stellar Info: GET https://ai-service-hub-15.emergent.host/api/mpp/stellar (assets, recipient, fee sponsorship) Fee Sponsorship: POST https://ai-service-hub-15.emergent.host/api/mpp/stellar/sponsor (NEXUS pays Stellar gas — agents need 0 XLM)

External Endpoints

URL	Method	Data Sent
`https://ai-service-hub-15.emergent.host/api/original-services/error-explain`	POST	Input parameters as JSON body

Security & Privacy

All data is sent to https://ai-service-hub-15.emergent.host over HTTPS/TLS.
No data is stored permanently; requests are processed and discarded.
Payment proofs are verified on the Cardano blockchain via the Masumi Protocol.
No filesystem access or shell execution required.

Model Invocation Note

This skill calls the NEXUS AI service API which uses LLM models (GPT-5.2, Claude Sonnet 4.5, GPT-4o) to process requests. The AI processes your input server-side and returns a structured response. You may opt out by not installing this skill.

Trust Statement

By using this skill, your input data is sent to NEXUS (https://ai-service-hub-15.emergent.host) for AI processing. Payments are non-custodial via the Masumi Protocol on Cardano. Only install if you trust NEXUS as a service provider. Visit https://ai-service-hub-15.emergent.host for full documentation.

Compare before choosing

Computed 10042,015

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 1007

event4u-app/agent-config

design-intelligence

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

Computed 1007

event4u-app/agent-config

existing-ui-audit

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

Computed 1007

event4u-app/agent-config

testing-anti-patterns

Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

What it does—and where it fits

Best for

Not for

Platform support, with evidence labels

Inspect first. Install second.

What the source asks the agent to do

When to use

Steps

Option A: x402 Standard (Recommended)

Option B: MPP Standard

Option C: Legacy Header

Static risk signals and limitations

Network access

Sends data out

Network access

Why each signal appears

Provenance and original SKILL.md

Error Explainer

When to use

Steps

Option A: x402 Standard (Recommended)

Option B: MPP Standard

Option C: Legacy Header

API Call

External Endpoints

Security & Privacy

Model Invocation Note

Trust Statement

Tags

Compare before choosing

ab-testing

design-intelligence

existing-ui-audit

testing-anti-patterns