Skip to content

Rename skill to container-tracking - #3

Merged
dodeja merged 2 commits into
mainfrom
rename-skill-container-tracking
Jul 22, 2026
Merged

Rename skill to container-tracking#3
dodeja merged 2 commits into
mainfrom
rename-skill-container-tracking

Conversation

@dodeja

Copy link
Copy Markdown
Member

Renames the shared skill from terminal49-mcp to container-tracking — the name should describe the capability, not the transport, and the plugin namespace already carries the Terminal49 branding (it surfaces as terminal49:container-tracking in Claude Code). Done pre-publish so it isn't a breaking change.

Updates the skill directory, frontmatter, validator checks, and all doc references.

🤖 Generated with Claude Code

dodejaand others added 2 commits July 22, 2026 14:11
The skill name should describe the capability, not the transport, and
the plugin namespace already carries the Terminal49 branding. Renamed
before first publish so nothing user-visible breaks.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Operator-first framing: bare identifier means status request, plain
operational language, lead with what needs attention
- State-dependent guidance: which attributes matter at each lifecycle
stage from booking through empty return
- Risk signals: ETA drift, 3+ day terminal dwell, LFD pressure, active
holds, rolls, detention
- Pickup-location logic: POD terminal vs inland rail ramp/destination
- Fleet queries rank by risk; richer trigger description
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:1bd2be96c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +116 to +118
- If the shipment has an inland destination or the route/events show a rail
leg, pickup happens at the inland ramp or destination terminal — report that
location and the rail arrival ETA, not the POD availability.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Require the rail leg to reach the inland destination

For shipments with an origin-side or other intermediate rail leg but a final destination at the POD, this or treats any rail movement as proof of inland pickup and instructs every supported client to suppress the relevant POD availability, holds, and LFD. Require the destination to be inland and the rail leg to connect the POD to that destination before reporting an inland pickup location.

AGENTS.md reference: AGENTS.md:L18-L19

Useful? React with 👍 / 👎.

@dodeja
dodeja merged commit a484bec into mainJul 22, 2026
1 check passed
@dodeja
dodeja deleted the rename-skill-container-tracking branch July 22, 2026 21:35
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@dodeja