Hi — we've published an agent-readable skill for integrating with the Corporate Cloud Consortium, a creator platform on the Internet Computer (mainnet canister ipchn-lqaaa-aaaam-qizkq-cai, live at corporatecloudconsortium.cloud). We'd like to request it be added to the Ecosystem Skills section of skills.internetcomputer.org.
We're following the same pattern as the Liquidium SDK ecosystem skill listed recently — a third-party skill hosted in our own org repo.
Repo: https://github.com/Corporate-cloud-consortium/CCC-skills
Skill path: skills/ccc-integration/SKILL.md
Install: npx skills add Corporate-cloud-consortium/CCC-skills/skills/ccc-integration
The skill covers NFT tier verification (ICRC-7, method list verified against the live canister's candid:service metadata), gated-content reading, and on-chain governance state. Frontmatter follows the Agent Skills spec used in this repo (name, description with do/don't-use guidance, license, metadata.title, metadata.category: Integration).
Happy to open a PR against the appropriate data file instead if you point me at the listing mechanism, and glad to make any changes needed to meet listing criteria.
Hi — we've published an agent-readable skill for integrating with the Corporate Cloud Consortium, a creator platform on the Internet Computer (mainnet canister ipchn-lqaaa-aaaam-qizkq-cai, live at corporatecloudconsortium.cloud). We'd like to request it be added to the Ecosystem Skills section of skills.internetcomputer.org.
We're following the same pattern as the Liquidium SDK ecosystem skill listed recently — a third-party skill hosted in our own org repo.
Repo: https://github.com/Corporate-cloud-consortium/CCC-skills
Skill path: skills/ccc-integration/SKILL.md
Install: npx skills add Corporate-cloud-consortium/CCC-skills/skills/ccc-integration
The skill covers NFT tier verification (ICRC-7, method list verified against the live canister's candid:service metadata), gated-content reading, and on-chain governance state. Frontmatter follows the Agent Skills spec used in this repo (name, description with do/don't-use guidance, license, metadata.title, metadata.category: Integration).
Happy to open a PR against the appropriate data file instead if you point me at the listing mechanism, and glad to make any changes needed to meet listing criteria.