{ "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": { "downloadMode": "redirect", "downloadUrl": "/downloads/arc-creator", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=arc-creator", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md", "references/arc-spec.md", "scripts/create_arc.sh" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "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." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/arc-creator", "agentPageUrl": "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" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "ARC Creator", "body": "Create FAIR Digital Objects following the nfdi4plants ARC specification v3.0.0." }, { "title": "Prerequisites", "body": "git and git-lfs installed\nARC Commander CLI at ~/bin/arc (optional but recommended)\nFor DataHUB sync: Personal Access Token for git.nfdi4plants.org or datahub.hhu.de" }, { "title": "Interactive ARC Creation Workflow", "body": "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." }, { "title": "Phase 1: Investigation Setup", "body": "Ask the user:\n\nInvestigation identifier (short, lowercase-hyphenated, e.g. cold-stress-arabidopsis)\nTitle (concise name for the investigation)\nDescription (textual description of the research goals)\nWhere to store the ARC locally (suggest /home/uranus/arc-projects//)\n\nThen run scripts/create_arc.sh and set investigation metadata via:\n\narc investigation update -i \"\" --title \"\" --description \"<desc>\"" }, { "title": "Phase 2: Studies", "body": "For each study, ask:\n\nStudy identifier (e.g. plant-growth)\nTitle and description\nOrganism (for Characteristic [Organism])\nGrowth conditions (temperature, light, medium, etc.)\nSource materials (what goes in — seeds, cell lines, etc.)\nSample materials (what comes out — leaves, roots, extracts, etc.)\nProtocols — does the user have protocol documents to include?\nFactors — what experimental variables are being tested? (e.g., temperature, genotype, treatment)\n\nCreate with:\n\narc study init --studyidentifier \"<id>\"\narc study update --studyidentifier \"<id>\" --title \"<title>\" --description \"<desc>\"\n\nCopy protocol files to studies/<id>/protocols/.\nCopy resource files to studies/<id>/resources/." }, { "title": "Phase 3: Assays", "body": "For each assay, ask:\n\nAssay identifier (e.g. proteomics-ms, rnaseq, sugar-measurement)\nMeasurement type (e.g., protein expression profiling, transcription profiling, metabolite profiling)\nTechnology type (e.g., mass spectrometry, nucleotide sequencing, plate reader)\nTechnology platform (e.g., Illumina NovaSeq, Bruker timsTOF)\nData files — where are the raw data files? (will go into assays/<id>/dataset/)\nProcessed data — any processed output files?\nProtocols — assay-specific protocols?\nPerformers — who performed this assay? (name, affiliation, role)\n\nCreate with:\n\narc assay init -a \"<id>\" --measurementtype \"<type>\" --technologytype \"<tech>\"\n\nCopy data to assays/<id>/dataset/, protocols to assays/<id>/protocols/." }, { "title": "Phase 4: Workflows (optional)", "body": "Ask if there are computational analysis steps. For each:\n\nWorkflow identifier (e.g. deseq2-analysis, heatmap-generation)\nDescription of what it does\nCode files (scripts, notebooks)\nDependencies (Python packages, R libraries, Docker image)\n\nPlace code in workflows/<id>/.\nNote: workflow.cwl is REQUIRED by spec but often created later. Inform user." }, { "title": "Phase 5: Runs (optional)", "body": "Ask if there are computation outputs. For each:\n\nRun identifier\nWhich workflow produced it\nOutput files (figures, tables, processed data)\n\nPlace outputs in runs/<id>/." }, { "title": "Phase 6: Contacts & Publications", "body": "Ask:\n\nInvestigation contacts (name, email, affiliation, role — at minimum the PI)\nPublications (if any — DOI, PubMed ID, title, authors)\n\nAdd via:\n\narc investigation person register --lastname \"<last>\" --firstname \"<first>\" --email \"<email>\" --affiliation \"<aff>\"" }, { "title": "Phase 7: Git Commit & DataHUB Sync", "body": "Configure git user:\n\ngit config user.name \"<name>\"\ngit config user.email \"<email>\"\n\nCommit:\n\ngit add -A\ngit commit -m \"Initial ARC: <investigation title>\"\n\nAsk if the user wants to push to a DataHUB. If yes:\n\nAsk which host (git.nfdi4plants.org, datahub.hhu.de, etc.)\nCreate remote repo (via browser or API)\nSet remote and push" }, { "title": "ISA Metadata Reference", "body": "For detailed ISA-XLSX fields, annotation table columns, and ontology references, read references/arc-spec.md." }, { "title": "Key Reminders", "body": "Assay data is immutable — never modify files in assays/<id>/dataset/ after initial placement\nStudies describe materials, assays describe measurements\nWorkflows are code, runs are outputs\nGit LFS for files > 100 MB: git lfs track \"*.fastq.gz\" \"*.bam\" \"*.raw\"\nDon't store ARCs on OneDrive/Dropbox — Git + cloud sync causes conflicts\nARC Commander CLI reference: arc <subcommand> --help" } ], "body": "ARC Creator\n\nCreate FAIR Digital Objects following the nfdi4plants ARC specification v3.0.0.\n\nPrerequisites\ngit and git-lfs installed\nARC Commander CLI at ~/bin/arc (optional but recommended)\nFor DataHUB sync: Personal Access Token for git.nfdi4plants.org or datahub.hhu.de\nInteractive ARC Creation Workflow\n\nGuide the user through these phases in order. Ask questions conversationally — don't dump all questions at once. Batch 2-4 related questions per message.\n\nPhase 1: Investigation Setup\n\nAsk the user:\n\nInvestigation identifier (short, lowercase-hyphenated, e.g. cold-stress-arabidopsis)\nTitle (concise name for the investigation)\nDescription (textual description of the research goals)\nWhere to store the ARC locally (suggest /home/uranus/arc-projects/<identifier>/)\n\nThen run scripts/create_arc.sh <path> <identifier> and set investigation metadata via:\n\narc investigation update -i \"<id>\" --title \"<title>\" --description \"<desc>\"\n\nPhase 2: Studies\n\nFor each study, ask:\n\nStudy identifier (e.g. plant-growth)\nTitle and description\nOrganism (for Characteristic [Organism])\nGrowth conditions (temperature, light, medium, etc.)\nSource materials (what goes in — seeds, cell lines, etc.)\nSample materials (what comes out — leaves, roots, extracts, etc.)\nProtocols — does the user have protocol documents to include?\nFactors — what experimental variables are being tested? (e.g., temperature, genotype, treatment)\n\nCreate with:\n\narc study init --studyidentifier \"<id>\"\narc study update --studyidentifier \"<id>\" --title \"<title>\" --description \"<desc>\"\n\n\nCopy protocol files to studies/<id>/protocols/. Copy resource files to studies/<id>/resources/.\n\nPhase 3: Assays\n\nFor each assay, ask:\n\nAssay identifier (e.g. proteomics-ms, rnaseq, sugar-measurement)\nMeasurement type (e.g., protein expression profiling, transcription profiling, metabolite profiling)\nTechnology type (e.g., mass spectrometry, nucleotide sequencing, plate reader)\nTechnology platform (e.g., Illumina NovaSeq, Bruker timsTOF)\nData files — where are the raw data files? (will go into assays/<id>/dataset/)\nProcessed data — any processed output files?\nProtocols — assay-specific protocols?\nPerformers — who performed this assay? (name, affiliation, role)\n\nCreate with:\n\narc assay init -a \"<id>\" --measurementtype \"<type>\" --technologytype \"<tech>\"\n\n\nCopy data to assays/<id>/dataset/, protocols to assays/<id>/protocols/.\n\nPhase 4: Workflows (optional)\n\nAsk if there are computational analysis steps. For each:\n\nWorkflow identifier (e.g. deseq2-analysis, heatmap-generation)\nDescription of what it does\nCode files (scripts, notebooks)\nDependencies (Python packages, R libraries, Docker image)\n\nPlace code in workflows/<id>/. Note: workflow.cwl is REQUIRED by spec but often created later. Inform user.\n\nPhase 5: Runs (optional)\n\nAsk if there are computation outputs. For each:\n\nRun identifier\nWhich workflow produced it\nOutput files (figures, tables, processed data)\n\nPlace outputs in runs/<id>/.\n\nPhase 6: Contacts & Publications\n\nAsk:\n\nInvestigation contacts (name, email, affiliation, role — at minimum the PI)\nPublications (if any — DOI, PubMed ID, title, authors)\n\nAdd via:\n\narc investigation person register --lastname \"<last>\" --firstname \"<first>\" --email \"<email>\" --affiliation \"<aff>\"\n\nPhase 7: Git Commit & DataHUB Sync\nConfigure git user:\ngit config user.name \"<name>\"\ngit config user.email \"<email>\"\n\nCommit:\ngit add -A\ngit commit -m \"Initial ARC: <investigation title>\"\n\nAsk if the user wants to push to a DataHUB. If yes:\nAsk which host (git.nfdi4plants.org, datahub.hhu.de, etc.)\nCreate remote repo (via browser or API)\nSet remote and push\nISA Metadata Reference\n\nFor detailed ISA-XLSX fields, annotation table columns, and ontology references, read references/arc-spec.md.\n\nKey Reminders\nAssay data is immutable — never modify files in assays/<id>/dataset/ after initial placement\nStudies describe materials, assays describe measurements\nWorkflows are code, runs are outputs\nGit LFS for files > 100 MB: git lfs track \"*.fastq.gz\" \"*.bam\" \"*.raw\"\nDon't store ARCs on OneDrive/Dropbox — Git + cloud sync causes conflicts\nARC Commander CLI reference: arc <subcommand> --help" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/IngoGiebel/arc-creator", "publisherUrl": "https://clawhub.ai/IngoGiebel/arc-creator", "owner": "IngoGiebel", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "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" } }