Profile
ccusage/ccusage
Profiles ccusage performance. An agent skill from ccusage/ccusage.
Leverage WebEx user profiles, presence status, and workspace context to personalize responses, route escalations, and coordinate team operations.
Apache-2.0Auto-check passed
Install Webex User Context
$ npx skills add automateyournetwork/netclaw --skill webex-user-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw webex-user-context --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/webex-user-context .claude/skills/webex-user-context && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "webex-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/webex-user-context into .claude/skills/webex-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webex-user-context", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/webex-user-contextType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill webex-user-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw webex-user-context --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/webex-user-context .agents/skills/webex-user-context && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "webex-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/webex-user-context into .agents/skills/webex-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webex-user-context", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill webex-user-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw webex-user-context --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/webex-user-context .cursor/skills/webex-user-context && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "webex-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/webex-user-context into .cursor/skills/webex-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webex-user-context", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/webex-user-context--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill webex-user-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw webex-user-context --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/webex-user-context .gemini/skills/webex-user-context && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "webex-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/webex-user-context into .gemini/skills/webex-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webex-user-context", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw webex-user-contextInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill webex-user-context -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/webex-user-context .github/skills/webex-user-context && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "webex-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/webex-user-context into .github/skills/webex-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webex-user-context", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill webex-user-context -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw webex-user-context --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/webex-user-context .opencode/skills/webex-user-context && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "webex-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/webex-user-context into .opencode/skills/webex-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webex-user-context", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
webex-user-context- GitHub stars
- 675
- Token cost
- ~1.5k tokens
- SKILL.md length
- 573 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Leverage WebEx user profiles, presence status, and workspace context to personalize responses, route escalations, and coordinate team operations.
- Works in 4 steps: Escalation Routing → Personalized Response Depth → Timezone-Aware Scheduling → …
- Checking who is available
- SKILL.md covers WebEx API Capabilities Used, User-Aware Behaviors, Team Awareness Features and WebEx Mentions, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Webex User Context is an agent skill from automateyournetwork/netclaw. Leverage WebEx user profiles, presence status, and workspace context to personalize responses, route escalations, and coordinate team operations. Use when checking who is available, routing an escalation, personalizing responses based on user role, or determining engineer availability before paging someone.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
When your agent uses it
- Checking who is available
- Routing an escalation
- Personalizing responses based on user role
- Determining engineer availability before paging someone
Example prompts
- “/webex-user-context”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 95bb17e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Webex User Context loads about 1.5k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 573 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from automateyournetwork/netclaw at commit 95bb17e, republished under its Apache-2.0 licence (© automateyournetwork). 573 words, ~1,490 tokens.
Download SKILL.mdSave it as
.claude/skills/webex-user-context/SKILL.md (or your agent's skills folder).- name
- webex-user-context
- description
- Leverage WebEx user profiles, presence status, and workspace context to personalize responses, route escalations, and coordinate team operations. Use when checking who is available, routing an escalation, personalizing responses based on user role, or determining engineer availability before paging someone.
- license
- Apache-2.0
- user-invocable
- true
WebEx User Context
WebEx API Capabilities Used
| API | Purpose |
|---|---|
| People -- List | Search workspace members by name, email, or orgId |
| People -- Get Details | View detailed profiles (displayName, emails, orgId, roles, avatar) |
| People -- Get My Own Details | Verify bot identity |
| Room Memberships -- List | See who is in a specific space |
| Messages -- List | Read recent messages for context |
| Webhooks | Receive real-time notifications for new messages |
User-Aware Behaviors
1. Escalation Routing
Before escalating an alert to a specific person:
- Look up the person -- Use People API to find them by email or displayName
- Check space membership -- Verify they are a member of the relevant space
- Check recent activity -- Look at recent messages to gauge availability
- Check profile role -- Use displayName, title, and orgId to determine their role
Escalation Decision Matrix:
| Status | Severity | Action |
|---|---|---|
| Active in space (recent messages) | Any | Mention directly with <@personId> |
| No recent activity | P1/P2 | Mention directly (they'll receive notification) |
| No recent activity | P3/P4 | Post to space, don't mention |
| Known off-hours (timezone) | P1 | Mention anyway (override for P1) |
| Known off-hours (timezone) | P2 | Try next person in rotation |
| Known off-hours (timezone) | P3/P4 | Post to space only |
2. Personalized Response Depth
Adjust response complexity based on who's asking.
From user profile title/role context:
| Role Context | Response Style |
|---|---|
| Network Engineer, CCIE | Full technical detail, CLI output, protocol specifics |
| NOC, Operations | Actionable steps, severity, impact summary |
| Manager, Director | Executive summary, business impact, timeline |
| Security, InfoSec | Focus on security implications, CVEs, compliance |
| Developer, DevOps | API perspectives, connectivity impact, service mapping |
| Help Desk, Support | Simple status, ETA, who to contact |
3. Timezone-Aware Scheduling
When scheduling reports or maintenance windows:
- Determine the requesting user's timezone from their profile or prior conversation context
- Present times in THEIR timezone (not just UTC)
- Warn if proposed maintenance window is outside their business hours
- Suggest alternatives that work across timezones for multi-region teams
4. Context from Previous Conversations
When a user asks a follow-up question:
- Check recent messages in the space and threads for context
- Reference previous reports or investigations
- Don't re-explain concepts they've already discussed
- Build on previous analysis rather than starting fresh
Show full SKILL.md (228 more words)Show less
Team Awareness Features
On-Call Roster Awareness
When NetClaw needs to escalate:
**Escalation Attempt**
Checking team availability...
- John Smith (Network Engineer) -- Active in space (last message 5 min ago) -- **SELECTED**
- Jane Doe (Senior NetEng) -- No recent activity (last seen 3h ago)
- Bob Wilson (NOC Analyst) -- Active in Incidents space
- Alice Chen (Net Ops Manager) -- CC'd on P1
Escalating to John Smith...Workload Context
If NetClaw sees a user is already active in multiple incident threads:
**Note:** John Smith is currently active in 2 other incident threads.
Consider routing to Bob Wilson if this is non-urgent.Handoff Between Shifts
When a shift change is approaching:
**Shift Handoff Summary for @nightshift_engineer**
**Active Items:**
1. R2 memory trending high (78% -> 82% over 8h) -- monitoring
2. SW1 firmware upgrade scheduled for 02:00 UTC -- prep done
3. R1 Loopback99 change completed and verified
**Pending:**
4. Waiting on ISP ticket #45678 for R3 circuit
5. Security audit scheduled for SW2 tomorrow
_Full context in NetClaw Reports space thread_WebEx Mentions
Use <@personId> syntax to mention specific users in WebEx messages:
<@Y2lzY29zcGFyazovL3VzL1BFT1BMRS8xMjM0NTY3ODk> -- R1 is showing CRITICAL CPU at 94%. Please investigate.For group notifications, mention all relevant space members or create a dedicated notification space.
Privacy and Boundaries
- Never expose user activity patterns, email addresses, or personal info to other users
- Only use profile information to improve routing and response quality
- Don't track user activity beyond immediate operational needs
- Respect engineer availability -- follow the escalation matrix
- Be transparent about what context you're using when personalizing responses
Integration with Other Skills
| Skill | User Context Enhancement |
|---|---|
| webex-network-alerts | Route to active, available engineers |
| webex-incident-workflow | IC assignment based on availability |
| webex-report-delivery | Adjust detail level per audience |
| All pyATS skills | Include requestor context in GAIT trail |
Failure Behavior
- On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
- For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in workspace/skills/webex-user-context of automateyournetwork/netclaw.
Open the folder on GitHubat commit 95bb17e
Compare with similar skills
Webex User Context next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Webex User Context this skillautomateyournetwork/netclaw | 675 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Profileccusage/ccusage | 19k | — | ~430 | Automated safety check: Pass | Custom licence | |
| Cpu ProfileClickHouse/ClickHouse | 50k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Codex Profilessickn33/agentic-awesome-skills | 47k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Collectors Snmp Profilesnetdata/netdata | 81k | — | ~3.1k | Automated safety check: Pass | GPL-3.0 | |
| Alloc ProfileClickHouse/ClickHouse | 50k | — | ~4.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cpu Profile
ClickHouse/ClickHouse
Profile a ClickHouse query using the sampling query profiler and system.tracelog.
Codex Profiles
sickn33/agentic-awesome-skills
Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEXHOME profiles for separate accounts, projects, and local state.
Collectors Snmp Profiles
netdata/netdata
Author or review Netdata SNMP polling profiles, ddsnmp parsing, topology/licensing/BGP rows and profile-format documentation.
Alloc Profile
ClickHouse/ClickHouse
Analyze a jemalloc (or other) allocation profile in collapsed stack format.
Competitor Profiling
sickn33/agentic-awesome-skills
When the user wants to research, profile, or analyze competitors from their URLs.
More from automateyournetwork/netclaw
All 120 skills in this repoEVE-NG Lab Topology Design
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
ACI Policy Change Deployment
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
Cisco ACI Fabric Health Audit
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
AWS Cloud Monitoring
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Questions about Webex User Context
What does Webex User Context do?
Leverage WebEx user profiles, presence status, and workspace context to personalize responses, route escalations, and coordinate team operations. Webex User Context is an agent skill from automateyournetwork/netclaw. Leverage WebEx user profiles, presence status, and workspace context to personalize responses, route escalations, and coordinate team operations.
When should I use Webex User Context?
Webex User Context fits situations like: checking who is available; routing an escalation; personalizing responses based on user role; determining engineer availability before paging someone.
How do I install Webex User Context in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill webex-user-context -a claude-code`. Or copy the skill folder (workspace/skills/webex-user-context in automateyournetwork/netclaw) into .claude/skills/webex-user-context in your project. Claude Code loads it when a task matches its description.
How do I install Webex User Context in Codex?
Run `npx skills add automateyournetwork/netclaw --skill webex-user-context -a codex`. Or copy the skill folder (workspace/skills/webex-user-context in automateyournetwork/netclaw) into .agents/skills/webex-user-context in your project. Codex loads it when a task matches its description.
Can I use Webex User Context in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill webex-user-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/webex-user-context, .gemini/skills/webex-user-context, .github/skills/webex-user-context and .opencode/skills/webex-user-context in your project.
What does Webex User Context need to run?
SKILL.md names no scripts, command-line tools or credentials: Webex User Context is instructions for the agent only.
Does Webex User Context access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Webex User Context safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Webex User Context use?
Webex User Context is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Webex User Context use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Webex User Context?
Skills that share tags, products or a category with Webex User Context: Profile (ccusage/ccusage, 19k stars), Cpu Profile (ClickHouse/ClickHouse, 50k stars), Codex Profiles (sickn33/agentic-awesome-skills, 47k stars) and Collectors Snmp Profiles (netdata/netdata, 81k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Webex User Context?
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 675 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 5, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.