ecoscope

Plugin ecoscope from marketplace ecoscope-skills in wildlife-dynamics/ecoscope-skills. Commands read from the repo's manifest — 23 days ago.

Skills (8)

• develop

  Use when the user asks to build, change, extend, or fix an ecoscope workflow — a new workflow from a description, a spec.yaml / config-form / dashboard-layout / test-case edit, "recompile and re-run the tests" — or whenever the work happens inside a workflow repo (spec.yaml + test-cases.yaml + layou

• e2e

  Use when the user asks for a Desktop end-to-end or Playwright test of an ecoscope workflow or to prove it in the real app — "add an E2E test for X", "does it run in Ecoscope Desktop", "Desktop says Success but shows nothing" — or when develop or publish proposes proving Desktop behaviour. Covers the

• guide

  Use when the user asks for a user guide, README, or end-user documentation for an ecoscope workflow, wants its form or dashboard explained for the people who run it, or asks whether the README still matches the workflow. Also fires from publish's guide gate or a develop handoff after a user-visible

• plan

  Use before designing when the user wants a new ecoscope workflow ("plan / spec out / write a PRD for a workflow that …") or a big multi-session improvement — a new data source, a new widget chain, a rename or migration, "rework the X workflow" — or when develop's planning offer is accepted. Produces

• publish

  Use when the user asks to publish, release, or cut a version of an ecoscope workflow, to open or fix its publish PR, or to get a finished develop branch through CI — "publish X", "bump the version and recompile for CI", "CI says generated files differ / VERSION.yaml must be greater than main". Also

• reference

  Use when answering questions about ecoscope workflow development that aren't attached to an active editing task — spec.yaml syntax, wt-compiler flags and errors, task discovery, rjsf overrides and form rendering, test-cases.yaml and mock-io, data connections (EarthRanger, SMART, GEE), publish gates

• review

  Use when the user explicitly asks for a review of ecoscope workflow work — "review this workflow / my changes / this branch", "is this ready for CI / for release?" — when /ecoscope:publish reaches its pre-release review gate, or when a review offered by develop is accepted; never fires unasked. Cove

• task

  Use when an ecoscope workflow needs a task the task libraries lack or an existing task updated — a task contract handed over by develop, "write / add a task that …", a task that raises inside a run or returns the wrong shape, a task the compiler cannot find, or a library change needing a release. Co

Similar plugins