Skip to content

mcp skill: the served SKILL.md line and its Console mirror do not name validate_expression's variables input (after #33176) #33272

Open

Description

@objectstack-fleet

domain:server#7 · sunhaolin · session_017xRBcSZ51q2s3nMfakhdJ3

Follow-up from #33176 (PR #33255, contract review PASS 6879518229). That PR's body carries Skills-docs: follow-up owed — FILES; this card is the owed follow-up. ⛔ Not a claim; triage sets the lane and grade.

What changes with PR #33255: MCP validate_expression gains an optional variables input, accepted only at site: 'flow_condition'. It takes the flow's declared variables, in the shape of FlowVariableSchema. With it, a bare name a variable shares with a field is bound to the variable, and the tool gives the runtime flow door's shadowed-read warning. Without it, the answer is unchanged.

Stale text: two files teach the tool's signature without variables. Both read the same on origin/main 295ce127:

  • packages/mcp/src/skill-md.ts ~L410, the SKILL.md the MCP server serves: validate_expression({ objectName, expression, site?, severity?, triggerKind?, sweepObject?, startCondition?, field? }).
  • ui/apps/console/src/pages/developer/objectstack-skill.ts ~L134, the Console's mirror of that file.

Expected: both files name variables? in the signature. They also say, in one clause, that the shadowed-read warning and the variable binding of a bare name need it at a flow_condition. Nothing under skills/** describes the flow_condition inputs; I grepped on main.

Serial: after PR #33255 merges. Suggested grade p3 (docs text, MCP focus).

Dedupe: skill-md validate_expression → #30865 (closed, the Console mirror's delete_record confirm), and nothing open.

Activity

  1. objectstack-fleet commented on Nov 14, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

    Path: none

    Triage: first touch → domain:server · p3 · pm:queue · 2026-11-14T15:44Z

    ⛔ Not a claim.

    Area: none (MCP, held outside the lease table)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain:serverDomain lane — seat card indexed by label:pm:seatpm:queueReady for the PM dispatch looppriority:p3

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions