Activity

1. adk-bot

   added

   tools[Component] This issue is related to tools[Component] This issue is related to tools

   on May 4, 2026
2. adk-bot

   added the

   Feature

   issue type on May 4, 2026
3. klateefa

   self-assigned this

   on May 4, 2026
4. klateefa commented on May 4, 2026

   

   klateefa

   on May 4, 2026

   More actions

   @henrywang0314 Thanks for the update. The request is currently being reviewed, and I will let you know if anything further is needed. Thank you for your understanding.
5. klateefa

   added

   needs review[Status] The PR/issue is awaiting review from the maintainer[Status] The PR/issue is awaiting review from the maintainer

   on May 4, 2026
6. rohityan commented on Jun 5, 2026

   

   rohityan

   on Jun 5, 2026

   Collaborator

   More actions

   /adk-issue-analyze
7. adk-bot commented on Jun 5, 2026

   

   adk-bot

   on Jun 5, 2026

   Collaborator

   More actions

   GitHub Issue #5579 Analysis: Support automatic artifact storage for files generated by skill toolset scripts

   Executive Summary

   1. What is broken? When executing agent skill scripts (via RunSkillScriptTool), files generated by the scripts (such as generated PDFs, images, data exports) are deleted immediately because the environment is executed within a nested tempfile.TemporaryDirectory that is discarded upon completion. There is no automatic detection or retention of these files.
   2. Is there a linked PR that fixes this issue? None.
   3. Recommendation: Should Fix (Medium Priority) — Standardizing dynamic output capture from skill script tools dramatically improves the usability of document, spreadsheet, and multimodal asset-generation skills without forcing developers to implement complex, custom storage workarounds.

   Detailed Analysis

   1. Root Cause Analysis ("What is broken?")

   When an agent invokes a skill script via the RunSkillScriptTool.run_async method, it utilizes an internal helper class _SkillScriptCodeExecutor to serialize and execute the workspace script using the underlying code executor (e.g., local, container, or VM-based sandbox).

   The execution flow decomposes as follows:

   • _build_wrapper_code designs a self-contained Python wrapper script.
   • The wrapper instantiates a temporary directory, switches the active working directory, and materializes skill assets locally:

     def _materialize_and_run():
       _orig_cwd = os.getcwd()
       with tempfile.TemporaryDirectory() as td:
         for rel_path, content in _files.items():
           ...
         os.chdir(td)
         try:
           # runs python with runpy or shell with subprocess.run()

   • Any files created during execution of the skill's Python code or shell scripts are saved locally inside td.
   • Once the script finishes or exits, the with tempfile.TemporaryDirectory() as td: context block is exited. This recursively wipes the temporary directory, purging all newly written documents, reports, or visual assets before they can be captured.

   2. Existing Pull Requests ("Is there a linked PR that fixes this issue?")

   • Linked PR: None
   • PR URL: N/A
   • Analysis: A thorough investigation across existing pull requests mentioning issue 5579 or containing relevant keywords ("artifact extraction", "skill outputs") confirms no corresponding PR or branch has been submitted to resolve this issue yet.

   3. Recommendation

   • Recommendation: Should Fix (Medium Priority)
   • Rationale:
     • Developer Experience: Generating data tables, charts, and reports is a first-class agent use case. Supporting automatic or opt-in file retention significantly saves developer lift.
     • Proposed Solution:
       1. Update _build_wrapper_code to perform a walk/diff of td after tool execution.
       2. Detect any newly created or modified files that are not part of the initial skill resource dictionary (_files).
       3. Encode these files as base64-serialized data within the JSON result envelope printed to standard output.
       4. Pass the tool_context to execute_script_async, allowing it to call await tool_context.save_artifact(...) to persist the discovered files in the ArtifactService automatically.
       5. Return the list of saved artifact filenames back to the agent in the tool result dictionary, e.g. "saved_artifacts": ["output_report.pdf"].
     • Complexity: Low to Medium. Minimal risk of side-effects since it operates completely inside the closed sandbox execution wrapper block.
8. a2105z commented on Aug 11, 2026

   

   a2105z

   on Aug 11, 2026

   Contributor

   More actions

   I'd like to take this — implementing automatic artifact capture for files generated by skill scripts (walk/diff the script tempdir after execution, save_artifact via tool_context, return saved_artifacts in the tool result).

   Following the bot analysis path in _build_wrapper_code / RunSkillScriptTool. Will open a PR shortly.
9. a2105z commented on Aug 11, 2026

   

   a2105z

   on Aug 11, 2026

   Contributor

   More actions

   Opened a fix in #6675

   Implementation follows the bot analysis: walk/diff the script tempdir after execution, persist new files via tool_context.save_artifact, and return saved_artifacts in the tool result.

   cc @klateefa @GWeale @DeanChensj
10. a2105z

    added a commit that references this issue on Aug 17, 2026

    feat(tools): Persist skill-script outputs as artifacts

    ...

    This issue will close once commit 140e5fa is merged into the 'main' branch.

    140e5fa
11. copybara-service

    closed this as completedin beaef0don Oct 2, 2026
12. middas-0706

    added a commit that references this issue on Oct 2, 2026

    feat: persist skill-script outputs as artifacts

    ...

    This issue will close once commit beaef0d is merged into the 'main' branch.

    beaef0d