Creator / Skill
package.zip
The original asset pack submitted by the creator. It is recommended to generate it with Relicex Skill, but it can also be prepared manually as a fallback.
Publish guide · Skill-first
Publish asset packs and turn them into reusable solution capability
Relicex recommends using Relicex Skill to turn memories, experience, prompts, workflows, and project knowledge into a package.zip draft. Asset packs can be sold standalone or composed into solutions that generate reuse royalties.
Skill creates package.zip draftsHuman confirmation before public listingStandalone sale and solution reuse
Recommended flow
Package assets first, then decide standalone sale or solution composition
The Skill-first flow reduces manual packaging mistakes and helps Relicex check structure, manifest details, risk hints, listing drafts, and future solution-reuse boundaries before publication.
01
Connect an AI tool
Open Connect AI and configure Relicex Skill so your AI or Agent can create asset drafts.
02
Create a package.zip draft
Let Skill organize memories, experience, prompts, templates, workflows, README, and manifest.
03
Review the draft
Confirm that content is accurate, authorized, and free of secrets, unauthorized data, malicious code, or malicious prompts.
04
Submit and encrypt
Relicex validates package.zip and generates ciphertext.zip for internal encrypted storage.
05
Publish the asset pack
Confirm title, description, price, license, subscription, and reference settings before publishing to Asset Library.
Three package names, three different roles
Creators, the platform, and buyers see different files. Creators mainly need to understand package.zip; ciphertext.zip is internal encrypted storage, and delivery.zip is generated for entitled buyers.
Platform internal
ciphertext.zip
The encrypted storage package generated by Relicex after validating package.zip. Creators usually do not handle it directly.
Buyer / Agent
delivery.zip
The authorized package generated for buyers or Agents, including receipt, watermark, and delivery instructions.
What Skill helps you package
Relicex Skill helps convert reusable knowledge into a reviewable, licensable, deliverable, and solution-reusable asset-pack draft. It can flag common issues, but final confirmation still belongs to the creator.
Content organization
Turn project knowledge, processes, prompts, templates, examples, and workflows into structured assets.
Manifest generation
Generate or complete manifest.json so Relicex can understand kind, files, tags, and delivery metadata.
Asset-pack draft
Draft title, description, category, tags, license scope, pricing, and solution-reuse suggestions for review.
Risk hints
Warn about secrets, tokens, private data, malicious code, malicious prompts, or malicious promotion.
License and reuse suggestions
Help separate personal use, commercial use, subscription access, standalone sale, solution references, remixes, and dependencies.
Pre-publish checks
Generate a confirmation checklist before the creator publishes the listing.
Asset pack kinds you can publish
You do not need to choose perfectly at the start. Tell Skill what you want to publish, and it can suggest an appropriate pack kind for your review.
memory_pack
Project memory, background material, long-term context, preferences, and factual collections.
experience_pack
Processes, templates, prompts, examples, playbooks, operating manuals, and best practices.
capability_pack
Reusable capabilities with input/output schemas, tool instructions, workflows, or execution guidance.
How asset packs become solutions
Publishing an asset pack is not the end of the workflow. A strong pack can be purchased directly, reused by your own solutions, or referenced by other creators' solutions under allowed licensing and settlement rules.
Standalone asset
The pack appears in Asset Library and can be purchased with its own entitlement.
Solution component
The pack can support a solution as memory, experience, capability, template, or evaluation evidence.
Reuse royalty
When a solution references the pack, settlement can attribute value back to the asset owner.
Confirm these before publishing
Skill can help detect common risks, but creators still need to confirm rights, safety, privacy, content accuracy, and pricing before public release.
I have the rights required to publish and license this asset pack.
If upstream content is referenced, it is authorized and truthfully declared.
No API tokens, cookies, private keys, passwords, or credentials are included.
No private user data, sensitive personal data, or unauthorized data is included.
No malicious code, backdoor, virus, or data exfiltration logic is included.
No malicious prompt, privilege escalation instruction, or malicious promotion is included.
The title, description, and tags are not false advertising.
Pricing, commercial license, subscription, and reference settings match my intent.
License, pricing, subscription, and reuse settings
Before publishing an asset pack, confirm these settings. See the earnings rules for solution reuse, upstream reference, and subscription allocation details.
Personal-use price
The price buyers pay for a standard personal-use entitlement.
Commercial use
If commercial use is allowed, enable it explicitly and set a commercial-use price.
Subscription inclusion
The pack can enter subscription entitlement and subscription revenue allocation pools.
Solution reuse / references
Other creators may use the pack as an upstream asset or solution component within allowed rules.
Supply
Limits how many units can be sold; confirm it matches your supply plan before publishing.
What happens after publication
After publication, buyers can purchase the asset pack directly or receive related entitlement through a complete solution. Relicex records entitlements, delivery, downloads, solution reuse, and Agent usage for refunds, reports, settlement, and risk review.
Refunds
Within 72 hours after payment, buyers can receive an automatic refund if they have not obtained the resource. After resource access or after 72 hours, refund requests require review.
Reports
Users can report severe mismatch, false advertising, malicious code, malicious prompt, malicious promotion, plagiarism, piracy, or unavailable resources.
Platform actions
After confirming severe issues, Relicex may delist listings, quarantine packages, freeze earnings, forfeit earnings, or restrict accounts.
Fallback publishing path: submit package.zip manually
The recommended path is still to create a package.zip draft with Relicex Skill. If you already prepared package.zip locally, you can submit it manually in Creator Center. Manual submission does not skip validation; after validation, Relicex still generates ciphertext.zip for internal storage.
Manual submission steps
- Prepare package.zip
- Confirm manifest.json and README.md
- Upload in Creator Center
- Let Relicex validate and generate ciphertext.zip
- Create or confirm listing metadata
- Complete rights and safety confirmation before publishing
Recommended package.zip structure
package.zip
├── manifest.json
├── README.md
├── prompts/
│ └── research.md
├── templates/
│ └── report.md
├── examples/
│ └── sample.md
└── assets/Minimal manifest.json example
{
"api_version": "relicex.pack.v0",
"kind": "experience_pack",
"id": "pricing-playbook-v1",
"version": "1.0.0",
"title": "Pricing Research Playbook",
"description": "A reusable workflow for pricing research.",
"tags": ["pricing", "research", "workflow"],
"files": {
"readme": "README.md",
"prompts": ["prompts/research.md"],
"templates": ["templates/report.md"],
"examples": ["examples/sample.md"]
},
"contains_personal_data": false,
"contains_code": false,
"requires_human_review": false
}FAQ
Should I submit package.zip or ciphertext.zip?
Submit package.zip. ciphertext.zip is generated by Relicex after validation and encryption, and creators usually do not handle it directly.
Will Skill publish my asset automatically?
No. Skill creates package.zip drafts by default. Public publication requires you to confirm content, rights, safety, and pricing.
Do buyers receive package.zip?
No. Entitled buyers receive delivery.zip, which includes a receipt, watermark, and delivery instructions.
Is manual publishing more advanced?
No. Manual submission is only a fallback. The recommended path remains creating a package.zip draft with Relicex Skill.
Do I need to write manifest.json by hand?
Not necessarily. Skill usually generates or completes it. If you manually submit package.zip, use the minimal structure on this page.
What happens if my asset is reported?
Reports enter admin review. If severe issues are confirmed, Relicex may delist, quarantine, freeze earnings, or take other actions.
Relicex Skill
Ready to publish?
Connect AI to create a package.zip draft with Relicex Skill, then review and publish from Creator Center.