10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
Paid client skill for Esri Workflow Smell Detector via x402 (Base/USDC). Use when you want to run a deterministic automation preflight scan on an ArcGIS Pro project snapshot by calling https://api.x402layer.cc/e/esri-smells (HTTP 402 payment flow).
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install danmaps/esri-smells-consumerInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
This skill helps an agent call the paid Smell Detector endpoint (x402 pay-per-request) using Base/USDC.
It does not host the service.
The expected input, project_snapshot, is the JSON artifact produced by the open-source ArcGIS Pro CLI (arcgispro-cli).
Recommended workflow:
arcgispro-cli to export a project snapshot/context artifact (safe-by-default, no raw data)This keeps a clean boundary:
arcgispro-cli) answers: what is in the project
POST https://api.x402layer.cc/e/esri-smells
Required JSON body:
{
"project_snapshot": { },
"constraints": {
"target": "arcpy" | "geoprocessing" | "agol",
"deployment": "desktop" | "server",
"max_runtime_sec": 300
}
}
summary
risk_score (0.0–1.0)issues[]
flags
version
requestHash
requestHash
pip install -r {baseDir}/requirements.txt
export PRIVATE_KEY="0x..."
export WALLET_ADDRESS="0x..."
python {baseDir}/scripts/call_smells.py path/to/project_snapshot.json
X-Payment.These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# Esri Workflow Smell Detector (Consumer Skill)
This skill helps an agent **call the paid Smell Detector** endpoint (x402 pay-per-request) using Base/USDC.
It does **not** host the service.
## How this relates to arcgispro-cli
The expected input, `project_snapshot`, is the JSON artifact produced by the open-source ArcGIS Pro CLI (`arcgispro-cli`).
Recommended workflow:
1) Use `arcgispro-cli` to export a project snapshot/context artifact (safe-by-default, no raw data)
2) Send that JSON to this paid endpoint for a deterministic preflight risk report
3) Use the report to decide whether to proceed with automation (ArcPy/GP/AGOL) and what to fix first
This keeps a clean boundary:
- Open core (`arcgispro-cli`) answers: **what is in the project**
- Paid layer (this service) answers: **how risky is it to automate, and why**
## Endpoint
- `POST https://api.x402layer.cc/e/esri-smells`
## Input
Required JSON body:
```json
{
"project_snapshot": { },
"constraints": {
"target": "arcpy" | "geoprocessing" | "agol",
"deployment": "desktop" | "server",
"max_runtime_sec": 300
}
}
```
## Output (guaranteed fields)
- `summary`
- `risk_score` (0.0–1.0)
- `issues[]`
- `flags`
- `version`
- `requestHash`
## Determinism
- Stateless
- No external network calls (beyond the paid endpoint itself)
- Same input produces same output
- Safe to cache by `requestHash`
## Pricing
- x402 pay-per-request on Base
- Target price: **$0.001** per call
## How to call (Python helper)
1) Install deps:
```bash
pip install -r {baseDir}/requirements.txt
```
2) Set wallet env (consumer wallet):
```bash
export PRIVATE_KEY="0x..."
export WALLET_ADDRESS="0x..."
```
3) Call the endpoint:
```bash
python {baseDir}/scripts/call_smells.py path/to/project_snapshot.json
```
### Notes
- The script implements the x402 HTTP 402 challenge flow and retries with `X-Payment`.
- If the endpoint is unreachable or the network rejects the payment, surface the error as-is.generate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.