Request: add CCC (Corporate Cloud Consortium) to Ecosystem Skills
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 13
- Avg merge
- 19h 10m
- Merged PRs (30d)
- 22
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Ecosystem Skills section and compare its existing Liquidium SDK entry with the requested CCC-skills/skills/ccc-integration/SKILL.md. Confirm the external skill and frontmatter, then add the listing through the repository's data mechanism; done means CCC appears in the published Ecosystem Skills section with the correct repository and install path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100