Gougoubi Create Condition

Create Gougoubi proposal conditions from minimal input (proposalId + conditionName) with deterministic defaults for deadline/tradeDeadline, validation, and t...

Security Scan

The skill is an instruction-only helper for creating on-chain Gougoubi proposal conditions and its requested resources and actions are consistent with that purpose.

Purpose & Capability

Name/description match the instructions: creating a condition for an existing Gougoubi proposal on BNB chain. Requiring a connected BNB wallet and resolving proposalId to a contract address are appropriate for an on-chain create-condition flow.

Instruction Scope

SKILL.md gives a deterministic step-by-step flow (resolve proposal, derive deadlines, validate, submit transaction). It leaves the exact resolution mechanism (browser E2E vs contract RPC) to the agent, which is reasonable but somewhat open-ended; ensure the agent does not read unrelated local files or private config to resolve proposal data.

Install Mechanism

Instruction-only skill with no install spec or bundled code, so nothing is written to disk or downloaded by the skill itself.

Credentials

The skill does not request environment variables or credentials in metadata, which is appropriate. It does require a connected BNB wallet in the agent runtime — this is proportional to the task, but users should confirm how the wallet is provided to the agent (external signer, injected key, hardware wallet) and ensure keys are not exposed.

Persistence & Privilege

always is false and there is no install-time component that requests permanent presence or modifies other skills. The skill can be invoked by the agent as expected.

Assessment

This skill is coherent for creating on-chain conditions, but before installing: (1) confirm how your agent runtime supplies the BNB wallet (hardware wallet or external signer is safer than stored private keys), (2) ensure the agent will prompt you before signing any transaction (SKILL.md explicitly forbids auto-accept), (3) verify network (BNB) and the proposal resolution method (web vs RPC) so you know which endpoints the agent will contact, and (4) do not expose private keys or broad credentials to the skill — it does not require any env vars, so supplying keys should be a deliberate, minimal action. If you need higher assurance, require manual confirmation for all on-chain operations and review any agent/browser automation steps that resolve proposal data on gougoubi.ai.

Create a new condition for an existing Gougoubi proposal from structured input.

Run Conditions

• Agent runtime must be configured with a usable BNB chain wallet address.
• Wallet must be connected before submitting any on-chain transaction.

Minimal Input (User Only)

{
  "proposalId": "0x... or proposal identifier",
  "conditionName": "Will Team A win the match?"
}

Proposal And Date Defaults

The skill must follow create-condition dialog default policy:

• Resolve proposalId to proposal contract address (proposalAddress) and fetch proposal detail.
• deadlineDateTime default: proposal deadline (proposalDeadline) in UTC ISO.
• deadlineTimezone default: user's local IANA timezone; fallback UTC.
• tradeDeadlineDateTime default: deadlineDateTime - 1 hour (general policy).
• tradeDeadlineTimezone default: same as deadlineTimezone.

Default safety clamp:

• deadlineDateTime must be greater than now.
• tradeDeadlineDateTime must be greater than now and not later than deadlineDateTime.
• If deadlineDateTime - 1 hour is not valid, set trade deadline to the nearest valid value that keeps tradeDeadlineDateTime <= deadlineDateTime (typically equal to deadlineDateTime when close to now).

Agent Auto-Fills

The skill auto-fills non-required fields:

• conditionImageUrl: empty string by default
• conditionRules: empty string by default
• skills: empty string by default
• isNormalized: true by default

Deterministic Steps

1. Validate minimal input (proposalId, conditionName).
2. Resolve proposalAddress from proposalId.
3. Load proposal detail and derive default condition deadline from proposal deadline.
4. Set timezone defaults (local timezone, fallback UTC).
5. Set trade deadline default to condition deadline minus 1 hour, then clamp to valid range.
6. Convert deadlineDateTime and tradeDeadlineDateTime to unix seconds.
7. Validate:
   • conditionName non-empty
   • deadline > now
   • tradeDeadline > now
   • tradeDeadline <= deadline
8. Ensure wallet is connected.
9. Submit contract call in canonical order:
   1. conditionName
   2. deadline
   3. tradeDeadline
   4. conditionImageUrl
   5. conditionRules
   6. skills
   7. isNormalized
10. Wait transaction confirmation.
11. Return normalized result.

Output

{
  "ok": true,
  "mode": "browser|contract",
  "txHash": "0x...",
  "proposalAddress": "0x...",
  "normalizedInput": {
    "proposalId": "",
    "proposalAddress": "",
    "conditionName": "",
    "deadlineDateTime": "",
    "deadlineTimezone": "",
    "tradeDeadlineDateTime": "",
    "tradeDeadlineTimezone": "",
    "defaultsApplied": true,
    "tradeDeadlinePolicy": "deadline-minus-1h-with-valid-clamp"
  },
  "warnings": []
}

Failure shape:

{
  "ok": false,
  "stage": "validation|resolve-proposal|create|confirm",
  "error": "reason",
  "retryable": true
}

Boundaries

• Do not use private credentials or private hosts.
• Do not auto-accept wallet signatures.
• Do not bypass user confirmation for irreversible on-chain actions.