Retrieve job input specifications and values from the Weaver system.
npx skills add https://github.com/crim-ca/weaver --skill job-inputs
Please help me install this Agent Skill. Skill: job-inputs Source: https://github.com/crim-ca/weaver/tree/main/.agents/skills/job-inputs Command: npx skills add https://github.com/crim-ca/weaver --skill job-inputs
This Skill helps users retrieve and document the input specifications and values that were provided when a job was executed, enabling debugging, result reproduction, and auditing.
Retrieve the inputs for a job by specifying its job ID.
High-intent search queries and answers about installing and using this skill.
To retrieve job inputs for a Weaver execution, you can use a tool that queries the Weaver API using the specific job identifier, returning the exact parameters and files provided during the original run.
Debugging a failed Weaver job execution involves fetching the original input specifications and values submitted for the job, allowing you to inspect the parameters that triggered the error.
Reproducing previous job results requires accessing the original input values and specifications submitted during the initial job execution, ensuring you run the process with the exact same parameters.
Yes, auditing job submissions in Weaver requires the unique job identifier to access and document the specific input specifications and values provided for that particular execution.
Yes, accessing job inputs allows you to retrieve both the parameter values and any file references that were supplied to the Weaver system when the job was originally executed.
crim-caManage and report on Weaver jobs with filtering and pagination.
novadbFetch NovaDB job execution logs and save them to a local file.
crim-caExtracts job execution logs with I/O streams and timestamps from Weaver API-driven systems.
crim-caRetrieves job output files and inline values securely via HTTPS from anywhere in the world, ensuring confidentiality and integrity of transmitted data with TLS encryption.
