Loxtep agent workspace

Skill LoxtepInc/loxtep-plugins-skills/skills/loxtep-agent-workspace

Loxtep plugins and skills for Cursor, Claude, Kiro, Antigravity, and Codex — MCP config and Customer MCPFrom the repository description

Install

npx -y skills add LoxtepInc/loxtep-plugins-skills --skill loxtep-agent-workspace

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, as published. Nobody here has run it

Agent orchestration workspace (Customer MCP)

Story S10: Issues, goals, agent projects, agents — this is the agent workspace, not data mesh repos (loxtep_workspace / loxtep_build).

When to use

"Create issue in agent workspace", "list goals", "agent_orchestration", "orchestration project" (agent project, not data project)

Prerequisites

MCP auth. All listed operations are organization-scoped; pass organization_id if the tool contract requires it (see platform tool definitions).

MCP tool and operations

Tool: loxtep_context
operation values (flat names): create_issue, list_issues, get_issue, create_goal, list_goals, get_goal, list_workstreams, create_workstream, get_workstream, list_agents, get_agent

Pitfalls

create_workstream ≠ create_project on loxtep_workspace. Naming collision in English — always pick the tool from user intent.
Data pipeline work → data-workflows + connect-external-system.
list_agents idle / last_heartbeat_at null does not mean inference HITL is broken. Steward inbox items with requesting_actor: pko-engine come from the PKO engine (procedure runs + approval backbone), not from seeded ConnectAgent / SemanticsAgent / Ontology Pipeline executor rows. Use loxtep_review.list_pending for HITL health; use list_agents only for executor wake/budget. See pko-engine-vs-seeded-agents.md.

Optional attribution

_metadata: { "skill_name": "loxtep-agent-workspace" }

Auth

loxtep-auth / login.

References

User story catalog