upload-artifact

Uploading project documentation as a versioned artifact involves providing a file path, title, and artifact type. The skill automates credential resolution and project selection to store files like PRDs and templates directly on the ClosedLoop platform.

The best way to save implementation plans for team knowledge sharing is by uploading them as formal project artifacts. This ensures files are correctly stored, version-managed, and easily discoverable within your team's ClosedLoop platform environment.

Yes, you can use MCP to upload files instead of direct script execution. The skill supports mode flexibility by falling back to Claude Code's MCP for convenient file uploads when direct API key authentication for script-based uploads is unavailable or not preferred.

Yes, the artifact upload process supports updating existing files through version updates. It resolves credentials, selects the appropriate project, and determines artifact typing to correctly manage and store new versions of previously uploaded documents.

You do not strictly need an API key to upload files as ClosedLoop artifacts. While an API key enables efficient direct script-based uploads, the skill can automatically fall back to using Claude Code's MCP for authentication and file management.