# Send ARC Creator to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "arc-creator", "name": "ARC Creator", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/IngoGiebel/arc-creator", "canonicalUrl": "https://clawhub.ai/IngoGiebel/arc-creator", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/arc-creator", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=arc-creator", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "references/arc-spec.md", "scripts/create_arc.sh" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "arc-creator", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T07:29:51.179Z", "expiresAt": "2026-05-06T07:29:51.179Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=arc-creator", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=arc-creator", "contentDisposition": "attachment; filename=\"arc-creator-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "arc-creator" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/arc-creator" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/arc-creator", "downloadUrl": "https://openagent3.xyz/downloads/arc-creator", "agentUrl": "https://openagent3.xyz/skills/arc-creator/agent", "manifestUrl": "https://openagent3.xyz/skills/arc-creator/agent.json", "briefUrl": "https://openagent3.xyz/skills/arc-creator/agent.md" } } ``` ## Documentation ### ARC Creator Create FAIR Digital Objects following the nfdi4plants ARC specification v3.0.0. ### Prerequisites git and git-lfs installed ARC Commander CLI at ~/bin/arc (optional but recommended) For DataHUB sync: Personal Access Token for git.nfdi4plants.org or datahub.hhu.de ### Interactive ARC Creation Workflow Guide the user through these phases in order. Ask questions conversationally — don't dump all questions at once. Batch 2-4 related questions per message. ### Phase 1: Investigation Setup Ask the user: Investigation identifier (short, lowercase-hyphenated, e.g. cold-stress-arabidopsis) Title (concise name for the investigation) Description (textual description of the research goals) Where to store the ARC locally (suggest /home/uranus/arc-projects//) Then run scripts/create_arc.sh and set investigation metadata via: arc investigation update -i "" --title "" --description "<desc>" ### Phase 2: Studies For each study, ask: Study identifier (e.g. plant-growth) Title and description Organism (for Characteristic [Organism]) Growth conditions (temperature, light, medium, etc.) Source materials (what goes in — seeds, cell lines, etc.) Sample materials (what comes out — leaves, roots, extracts, etc.) Protocols — does the user have protocol documents to include? Factors — what experimental variables are being tested? (e.g., temperature, genotype, treatment) Create with: arc study init --studyidentifier "<id>" arc study update --studyidentifier "<id>" --title "<title>" --description "<desc>" Copy protocol files to studies/<id>/protocols/. Copy resource files to studies/<id>/resources/. ### Phase 3: Assays For each assay, ask: Assay identifier (e.g. proteomics-ms, rnaseq, sugar-measurement) Measurement type (e.g., protein expression profiling, transcription profiling, metabolite profiling) Technology type (e.g., mass spectrometry, nucleotide sequencing, plate reader) Technology platform (e.g., Illumina NovaSeq, Bruker timsTOF) Data files — where are the raw data files? (will go into assays/<id>/dataset/) Processed data — any processed output files? Protocols — assay-specific protocols? Performers — who performed this assay? (name, affiliation, role) Create with: arc assay init -a "<id>" --measurementtype "<type>" --technologytype "<tech>" Copy data to assays/<id>/dataset/, protocols to assays/<id>/protocols/. ### Phase 4: Workflows (optional) Ask if there are computational analysis steps. For each: Workflow identifier (e.g. deseq2-analysis, heatmap-generation) Description of what it does Code files (scripts, notebooks) Dependencies (Python packages, R libraries, Docker image) Place code in workflows/<id>/. Note: workflow.cwl is REQUIRED by spec but often created later. Inform user. ### Phase 5: Runs (optional) Ask if there are computation outputs. For each: Run identifier Which workflow produced it Output files (figures, tables, processed data) Place outputs in runs/<id>/. ### Phase 6: Contacts & Publications Ask: Investigation contacts (name, email, affiliation, role — at minimum the PI) Publications (if any — DOI, PubMed ID, title, authors) Add via: arc investigation person register --lastname "<last>" --firstname "<first>" --email "<email>" --affiliation "<aff>" ### Phase 7: Git Commit & DataHUB Sync Configure git user: git config user.name "<name>" git config user.email "<email>" Commit: git add -A git commit -m "Initial ARC: <investigation title>" Ask if the user wants to push to a DataHUB. If yes: Ask which host (git.nfdi4plants.org, datahub.hhu.de, etc.) Create remote repo (via browser or API) Set remote and push ### ISA Metadata Reference For detailed ISA-XLSX fields, annotation table columns, and ontology references, read references/arc-spec.md. ### Key Reminders Assay data is immutable — never modify files in assays/<id>/dataset/ after initial placement Studies describe materials, assays describe measurements Workflows are code, runs are outputs Git LFS for files > 100 MB: git lfs track "*.fastq.gz" "*.bam" "*.raw" Don't store ARCs on OneDrive/Dropbox — Git + cloud sync causes conflicts ARC Commander CLI reference: arc <subcommand> --help ## Trust - Source: tencent - Verification: Indexed source record - Publisher: IngoGiebel - Version: 1.0.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T07:29:51.179Z - Expires at: 2026-05-06T07:29:51.179Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/arc-creator) - [Send to Agent page](https://openagent3.xyz/skills/arc-creator/agent) - [JSON manifest](https://openagent3.xyz/skills/arc-creator/agent.json) - [Markdown brief](https://openagent3.xyz/skills/arc-creator/agent.md) - [Download page](https://openagent3.xyz/downloads/arc-creator)