Digital Labour

This skill is functionally what it says: it forwards your agent inputs to an external Digital Labour API and returns results. Before installing, consider: - Data sensitivity: any inputs you send (documents, customer data, financials) will be transmitted to the configured BASE_URL. By default the skill uses a production third-party URL; if you do not explicitly set DIGITAL_LABOUR_API_URL you may send data to that service unintentionally. Do not use with sensitive data unless you trust and have reviewed the service's privacy and retention policies. - Missing declaration: the client will include an X-Api-Key header if DIGITAL_LABOUR_API_KEY is set, but that env var is not documented in the skill metadata — confirm expected auth methods with the publisher. - Pipeline behavior: the shipped workflows.json uses placeholders like $FROM_STEP_1.leads[0].company, but the pipeline runner performs only simple $KEY string substitution and stores prior step results as JSON strings. Expect the provided pipelines to behave incorrectly; test on non-sensitive inputs and ask the publisher for clarification or a fix. - Verification: run health/agents against a benign local or controlled endpoint first, or override DIGITAL_LABOUR_API_URL to a test server, to observe behavior. If you intend to use it in production, request from the publisher: (1) clear documentation of env vars and auth, (2) an explanation of data retention and access controls for the API, and (3) a corrected pipeline substitution mechanism if you plan to use the provided multi-step workflows.