job-results

Retrieves job output files and inline values securely via HTTPS from anywhere in the world, ensuring confidentiality and integrity of transmitted data with TLS encryption.

30|6|Updated Mar 5, 2019
One-click install
npx skills add https://github.com/crim-ca/weaver --skill job-results
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: job-results
Source: https://github.com/crim-ca/weaver/tree/main/.agents/skills/job-results
Command: npx skills add https://github.com/crim-ca/weaver --skill job-results

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the retrieval of output results from completed jobs, allowing for efficient access to files and inline values.

Core Features & Use Cases

  • Retrieve Results: Download output files or access inline values from jobs that have succeeded.
  • File Management: Download files locally or access them via provided URLs.
  • Use Case: After a job runs to completion, use this Skill to quickly download the output files or retrieve any inline values you need.

Quick Start

Retrieve the results of a completed job with the ID 'a1b2c3d4-e5f6-7890-abcd-ef1234567890' and download the output files to the 'outputs' directory.

Frequently Asked Questions about job-results

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I download job output files after a job has succeeded?

To download job output files after completion, you can use a skill that fetches results via the Weaver API and saves them locally to a specified directory. This allows you to retrieve outputs from jobs with a 'succeeded' status.

Can I retrieve inline values from completed jobs instead of downloading files?

Yes, you can retrieve inline values from completed jobs instead of downloading files. The Weaver API facilitates the retrieval of inline values directly, provided the job has a 'succeeded' status.

What do I need to access job outputs using the Weaver API?

To access job outputs using the Weaver API, you need API access and a job that has reached completion with a 'succeeded' status. You also need the specific job ID to fetch the corresponding outputs.

What is the best way to manage Weaver API job outputs locally?

The best way to manage Weaver API job outputs locally is to use a retrieval tool that fetches files via provided URLs or downloads them directly to a designated directory. This streamlines output management after job completion.

Why can't I fetch results for a job that is still running?

You cannot fetch results for a job that is still running because output retrieval requires the job to have a 'succeeded' status. The mechanism relies on job completion to ensure the results are fully generated and available.

Does job output retrieval work with any Weaver API job ID?

Job output retrieval works with any Weaver API job ID that corresponds to a job with a 'succeeded' status. You must provide the specific job ID to fetch and manage the associated output files or inline values.