There are many AI apps or channels for you to install an AI skill. Pick whichever of these matches how you use AI. Here are some for your reference.
In grok.com (browser or desktop)
archview.ziponto the upload panel.See the README.md
archview.zip.archview folder into your skills directory:
~/.claude/skills/archview.claude/skills/archview inside your repo/v1/skills endpoint to get a skill_id.skill_id in the container.skills parameter of a Messages API call, alongside the code execution tool. For example:import anthropic
client = anthropic.Anthropic()
response = client.beta.messages.create(
model="claude-sonnet-4-6",
max_tokens=4096,
betas=["code-execution-2025-08-25", "skills-2025-10-02"],
container={
"skills": [
{"type": "custom", "skill_id": "YOUR_ARCHVIEW_SKILL_ID", "version": "latest"}
]
},
tools=[{"type": "code_execution_20250825", "name": "code_execution"}],
messages=[
{"role": "user", "content": "Create an architecture view for my order processing system"}
],
)
Custom skills uploaded via the API are shared across your whole workspace.
If you have an eligible ChatGPT workspace:
Open ChatGPT.
Open Plugins in the sidebar.
Open Plugin Directory → Skills.
Select Create → Upload from your computer.
Select the archview.zip.
Wait for the security scan.
Install it.
For a personal Plus account: if you don’t see Skills, there isn’t currently a command-line workaround that installs a personal Skill into the ChatGPT UI. Use Codex or the API instead.
For a local Skill, this is probably the option you want. Codex CLI uses the Agent Skills format, so you can install the Skill into the appropriate Codex Skills directory rather than uploading it to the API.
First install/update Codex:
npm install -g @openai/codex
Then authenticate:
codex --login
Install the ArchView Skill (archview.zip). Create the Codex Skills directory if necessary:
mkdir -p ~/.codex/skills
Unzip the archview.zip there:
unzip -q archview.zip -d ~/.codex/skills/
The Codex app uses the same general Skills ecosystem.
mkdir -p ~/.codex/skills
unzip -q archview.zip -d ~/.codex/skills/
This is the other good option if you want your Skill to be managed centrally and used by an API application. Set your API key:
export OPENAI_API_KEY="sk-..."
Then upload the ZIP:
curl https://api.openai.com/v1/skills \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-F "files=@archview.zip"
The Skills API supports creating a Skill from a directory upload or a single ZIP file. (OpenAI Developers) The response will contain something like:
{
"id": "skill_abc123",
"name": "archview",
"default_version": "...",
"latest_version": "..."
}
Save the id, something like: skill_abc123. That’s the Skill ID your API application can reference.
curl https://api.openai.com/v1/skills \
-H "Authorization: Bearer $OPENAI_API_KEY"
curl https://api.openai.com/v1/skills/skill_abc123 \
-H "Authorization: Bearer $OPENAI_API_KEY"
curl -X DELETE \
https://api.openai.com/v1/skills/skill_abc123 \
-H "Authorization: Bearer $OPENAI_API_KEY"
In the Gemini ecosystem, the mechanism to publish a custom capability or tool depends on whether you are targeting everyday consumer/workspace users or developer interfaces like the Gemini CLI.
archview.zip file:gemini skills install ./archview.zip
Usage: Activate the skill in your prompt or call it directly:
gemini --skill skill-name "Run your request here"
If you are using the Gemini Web UI or an extension manager UI:
archview.zip from your file browser and click Confirm.@archview followed by your prompt.If you are developing a local app using the google-generativeai package, unpack the skill directly into your project directory to register its function calling definitions:
Unzip archview.zip into your project’s ./skills directory:
unzip archview.zip -d ./skills/
Load and register the unzipped skill modules within your Python code:
Installing a archview.zip across modern AI tools (Cursor, Pi, Windsurf, Roo Code, OpenCode, etc.) follows a consistent standard: unpacking the .zip so that a folder containing SKILL.md rests in the tool’s designated skills folder.
Cursor supports both global and project-level skills.
~/.cursor/skills/<project-root>/.cursor/skills/Menu / GUI Option:
.cursor at the root, and a skills subfolder inside it (e.g., .cursor/skills/).archview.zip directly into that skills/ folder so it looks like .cursor/skills/archview/SKILL.md.Ctrl+Shift+P / Cmd+Shift+P > Developer: Reload Window).Pi implements the standard Agent Skills directory model.
~/.pi/agent/skills/ or ~/.agents/skills/<project-root>/.pi/skills/Command Line:
# Global installation:
mkdir -p ~/.pi/agent/skills && unzip archview.zip -d ~/.pi/agent/skills/
# Project-level installation:
mkdir -p .pi/skills && unzip archview.zip -d .pi/skills/
Interactive Menu Command:
If running Pi interactively, load or toggle skills via the settings menu:
/settings inside Pi > Toggle enableSkillCommands or verify loaded paths./skill:archview.Windsurf stores skills in project or global settings directories.
~/.codeium/windsurf/skills/<**project-root>/.windsurf/skills/Command Line:
# Project-level (Recommended):
mkdir -p .windsurf/skills && unzip archview.zip -d .windsurf/skills/
# Global:
mkdir -p ~/.codeium/windsurf/skills && unzip archview.zip -d ~/.codeium/windsurf/skills/
Menu Option:
... (three dots) in the top-right corner > Select Skills.archview.zip contents into that folder.