The `receiver_writer` and `published_reader` HTTP profiles target the canonical PostgreSQL database named `plantgeo`. Railway-generated PostgreSQL URLs use the plain `postgresql` scheme; `Settings` no
Imported from Escherbridge/plantgeo (services/agri-data-service/src/agri_data_service/AGENTS.md). Install upstream with npx skills add Escherbridge/plantgeo --skill agri_data_service. Copyright stays with the author.
Agri data service application contracts
Production database target
The receiver_writer and published_reader HTTP profiles target the canonical PostgreSQL
database named plantgeo. Railway-generated PostgreSQL URLs use the plain postgresql scheme;
Settings normalizes that scheme to postgresql+asyncpg before validating the target.
Keep the database-name check in the profile resolver. It makes an accidental reference to the
legacy Aevani database named railway fail during Sanic startup with an explicit configuration
error instead of surfacing as repeated opaque /ready failures. Command-scoped and local DSNs
remain portable and continue to use the shared completeness validator without this production
target restriction.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/escherbridge-plantgeo-agri-data-service/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "escherbridge-plantgeo-agri-data-service",
"kind": "skill",
"name": "agri_data_service",
"description": "The `receiver_writer` and `published_reader` HTTP profiles target the canonical PostgreSQL database named `plantgeo`. Railway-generated PostgreSQL URLs use the plain `postgresql` scheme; `Settings` normalizes that scheme to `postgresql+asyncpg` before validating the target.",
"publisher": "Escherbridge",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"The `receiver_writer` and `published_reader` HTTP profiles target the canonical PostgreSQL database named `plantgeo`. Railway-generated PostgreSQL URLs use the plain `postgresql` scheme; `Settings` normalizes that scheme to `postgresql+asyncpg` before validating the target."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/Escherbridge/plantgeo",
"path": "services/agri-data-service/src/agri_data_service/AGENTS.md",
"ref": "5ee00219ac85809b1fc6c79ab96cd9df01bbbe24",
"url": "https://github.com/Escherbridge/plantgeo/blob/5ee00219ac85809b1fc6c79ab96cd9df01bbbe24/services/agri-data-service/src/agri_data_service/AGENTS.md",
"key": "Escherbridge/plantgeo/services/agri-data-service/src/agri_data_service/AGENTS.md"
}
},
"instructions": "# Agri data service application contracts\n\n## Production database target\n\nThe `receiver_writer` and `published_reader` HTTP profiles target the canonical PostgreSQL\ndatabase named `plantgeo`. Railway-generated PostgreSQL URLs use the plain `postgresql` scheme;\n`Settings` normalizes that scheme to `postgresql+asyncpg` before validating the target.\n\nKeep the database-name check in the profile resolver. It makes an accidental reference to the\nlegacy Aevani database named `railway` fail during Sanic startup with an explicit configuration\nerror instead of surfacing as repeated opaque `/ready` failu",
"cost": {
"context_tokens": 187
}
}
Fetch it by URL: GET /api/v1/registry/escherbridge-plantgeo-agri-data-service/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
