Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
A skill your agent uses when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics…
Install Ipsn Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-workflow --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/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/IPSN-Skills/skills/ipsn-workflow .claude/skills/ipsn-workflow && 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 "ipsn-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-workflow into .claude/skills/ipsn-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-workflow", 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/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-workflowType 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 brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/IPSN-Skills/skills/ipsn-workflow .agents/skills/ipsn-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ipsn-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-workflow into .agents/skills/ipsn-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-workflow", 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 brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/IPSN-Skills/skills/ipsn-workflow .cursor/skills/ipsn-workflow && 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 "ipsn-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-workflow into .cursor/skills/ipsn-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-workflow", 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/brycewang-stanford/Awesome-Journal-Skills.git --path IPSN-Skills/skills/ipsn-workflow--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 brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/IPSN-Skills/skills/ipsn-workflow .gemini/skills/ipsn-workflow && 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 "ipsn-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-workflow into .gemini/skills/ipsn-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-workflow", 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 brycewang-stanford/Awesome-Journal-Skills ipsn-workflowInstalls 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 brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/IPSN-Skills/skills/ipsn-workflow .github/skills/ipsn-workflow && 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 "ipsn-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-workflow into .github/skills/ipsn-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-workflow", 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 brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/IPSN-Skills/skills/ipsn-workflow .opencode/skills/ipsn-workflow && 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 "ipsn-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-workflow into .opencode/skills/ipsn-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-workflow", 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
ipsn-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 595 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics…
- Planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline
- SKILL.md covers Milestones, Backward plan from the…, The merger and calendar reality and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Double-blind submission
What it does
Ipsn Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Deployment. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline
- Double-blind submission
- Deployment and hardware logistics
- The Best Research Artifact Award
Example prompts
- “/ipsn-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. 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
Ipsn Workflow loads about 1.3k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 595 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 brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 595 words, ~1,310 tokens.
Download SKILL.mdSave it as
.claude/skills/ipsn-workflow/SKILL.md (or your agent's skills folder).- name
- ipsn-workflow
- description
- Use when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.
IPSN Workflow
Use this as the project-management skill for an IPSN-lineage submission. Replace every date with the current official timetable and work backwards from the successor (SenSys) deadline at CPS-IoT Week. The single biggest planning fact: IPSN no longer runs standalone — it merged into SenSys (Embedded AI and Sensing Systems), so plan against the current SenSys call, keeping the IP-vs-SPOTS instinct.
IPSN had no standing editor-in-chief and no APC; rotating leadership was the per-edition General Chair(s) and per-track (IP / SPOTS) Program Chairs under CPS-IoT Week, ACM SIGBED, and IEEE. The cost model is registration; at least one author presents. Re-check the successor's organizing-committee page rather than carrying a name forward.
Milestones
- Venue + track fit: confirm the IPSN lineage over MobiSys/MobiCom/INFOCOM/RTAS, and pick IP vs
SPOTS (
ipsn-topic-selection). - Evidence lock: freeze the testbed, ground-truth reference, baselines, energy/latency measurement setup, and the dataset/firmware artifact contents.
- Deployment window (if applicable): schedule field time early — a bridge, building, or wildlife deployment cannot be redone in the final week and is weather/permit-bound.
- Registration/abstract: submit real title, abstract, authors, track, and conflicts by the earlier cutoff.
- Submission: upload the anonymized PDF and dataset/firmware link on HotCRP.
- Rebuttal (if offered): correct misreadings and supply any measured number a reviewer flagged.
- Decision: archive reviews, rebuttal, and every submitted version.
- Acceptance: prepare the dual ACM/IEEE camera-ready, pursue the Best Research Artifact Award and ACM badges, register, and present.
Backward plan from the submission deadline
| Weeks out (heuristic) | Sensor-systems milestone |
|---|---|
| 12+ | Track chosen; testbed and ground-truth reference decided; deployment permits/weather scheduled |
| 10 | Hardware/firmware frozen; power-measurement harness built and validated |
| 8 | Data collection / deployment complete; raw traces, energy logs, and calibration archived |
| 6 | Analysis done; accuracy/energy/latency budgets computed; baselines run under equal conditions |
| 4 | Full draft on the ACM template (two-column, ≤12 pp); artifact assembled and anonymized |
| 3 | Internal mock review by a sensor-systems reader; check the IP/SPOTS framing holds |
| 2 | Limits hardened, related-work delta sharpened, page budget met |
| 1 | Double-blind sweep on PDF, board photos, scope screenshots, testbed names, dataset links |
| 0 | Register/track-select by the earlier cutoff, then paper + artifact link on HotCRP |
These offsets are planning heuristics only — anchor every one to the current CPS-IoT Week / successor Important Dates page.
Show full SKILL.md (235 more words)Show less
The merger and calendar reality
- IPSN's last standalone edition was IPSN 2024 (Hong Kong). The live target is the next SenSys edition at CPS-IoT Week; SenSys 2026 (Saint Malo) had a 13 Nov 2025 paper deadline, so the next edition's deadline is 待核实 — confirm before planning.
- Deployment lead time is the hidden critical path. Unlike a software paper, a sensing paper's schedule is bounded by physical access (a bridge closure window, a field season, a hardware fabrication run). Missing the deadline often costs a full year and a deployment window.
Failure modes by stage
- Testbed still moving at week 4 forces last-minute measurement nobody has audited — the classic evidence-realism reject.
- Leaving anonymization to the final week is how a lab-logo board photo or a named testbed leaks identity under double-blind review.
- Skipping the mock review forfeits the one chance to hear "your baseline is simulated" or "you never report energy" from a friend instead of a reviewer.
- Treating the rebuttal as decisive — it is narrow; the measured evidence in the paper carries the argument.
- Assuming IPSN still runs — check the successor venue before anything else.
Coordination notes
- Assign one owner for the artifact/dataset/firmware release and another for the double-blind sweep (including hardware imagery); shared ownership is how both slip.
- Archive the exact submitted PDF, artifact, raw traces, and calibration — the rebuttal and camera-ready must quote them precisely, and the artifact award needs them.
Output format
[Current stage] idea / evidence / deployment / writing / submitted / rebuttal / accepted
[Venue + track] successor (SenSys) edition + IP/SPOTS, with the next deadline (or 待核实)
[Critical path] <three tasks that determine readiness — often deployment-bound>
[Risk register] <page budget / anonymity / evidence-realism / energy accounting / artifact / deployment window>
[Owner map] <task -> person or role>© brycewang-stanford, MIT. 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 IPSN-Skills/skills/ipsn-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ipsn Workflow 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 |
|---|---|---|---|---|---|---|
| Ipsn Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 62k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Ipsn Workflow
What does Ipsn Workflow do?
A skill your agent uses when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics…. Ipsn Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.
When should I use Ipsn Workflow?
Ipsn Workflow fits situations like: planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline; double-blind submission; deployment and hardware logistics; the Best Research Artifact Award.
How do I install Ipsn Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a claude-code`. Or copy the skill folder (IPSN-Skills/skills/ipsn-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ipsn-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Ipsn Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a codex`. Or copy the skill folder (IPSN-Skills/skills/ipsn-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ipsn-workflow in your project. Codex loads it when a task matches its description.
Can I use Ipsn Workflow 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 brycewang-stanford/Awesome-Journal-Skills --skill ipsn-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ipsn-workflow, .gemini/skills/ipsn-workflow, .github/skills/ipsn-workflow and .opencode/skills/ipsn-workflow in your project.
What does Ipsn Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Ipsn Workflow is instructions for the agent only.
Does Ipsn Workflow 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 Ipsn Workflow 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 Ipsn Workflow use?
Ipsn Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ipsn Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Ipsn Workflow?
Skills that share tags, products or a category with Ipsn Workflow: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ipsn Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.