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 auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the…
Install Ipsn Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-submission --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-submission .claude/skills/ipsn-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-submission into .claude/skills/ipsn-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-submission --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-submission .agents/skills/ipsn-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-submission into .agents/skills/ipsn-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-submission --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-submission .cursor/skills/ipsn-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-submission into .cursor/skills/ipsn-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-submission --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-submission .gemini/skills/ipsn-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-submission into .gemini/skills/ipsn-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/ipsn-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-submission into .github/skills/ipsn-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-submission", 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-submission -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-submission --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-submission .opencode/skills/ipsn-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-submission into .opencode/skills/ipsn-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 710 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the…
- Works in 7 steps: Confirm the live successor (SenSys)… → Freeze the body early; measurements and… → Register… → …
- Auditing an IPSN-lineage submission for HotCRP readiness
- SKILL.md covers Pick the track before the PDF, Format and page budget, Double-blind sweep (hardware… and Dataset and artifact at…, plus 4 more sections
- Calls pdftotext
What it does
Ipsn Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the double-blind sweep for hardware/deployment papers, dataset/artifact links, and desk-reject triage — routed to the current successor (SenSys) call because IPSN no longer runs standalone.
Its SKILL.md is about 1.6k 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
- Auditing an IPSN-lineage submission for HotCRP readiness
- Covering the IP-vs-SPOTS track choice
- The ACM Primary Article Template and ≤12-page inclusive budget
- The double-blind sweep for hardware/deployment papers
Example prompts
- “/ipsn-submission”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Confirm the live successor (SenSys) call, its deadline, and whether the track split survives.
- Freeze the body early; measurements and figures can be re-plotted, the argument cannot.
- Register title/abstract/authors/conflicts and pick the track before the cutoff.
- Build the anonymized dataset/firmware package and place its link and release statement in the paper.
- Run the mechanical anonymity checks on the final PDF and archive, plus an eyes-on pass over
- Fill every HotCRP field — topic tags matching your track, conflicts for every coauthor's
- Re-download the uploaded PDF and read it cold.
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.6k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 710 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). 710 words, ~1,607 tokens.
Download SKILL.mdSave it as
.claude/skills/ipsn-submission/SKILL.md (or your agent's skills folder).- name
- ipsn-submission
- description
- Use when auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the double-blind sweep for hardware/deployment papers, dataset/artifact links, and desk-reject triage — routed to the current successor (SenSys) call because IPSN no longer runs standalone.
IPSN Submission
Run this audit before uploading. IPSN research papers were double-blind, on the ACM Primary
Article Template, ≤12 pages inclusive of everything, submitted through HotCRP — and split
into the IP and SPOTS tracks. IPSN merged into SenSys (Embedded AI and Sensing Systems)
from 2025-2026, so reopen the current SenSys call first: the numbers below are the IPSN 2024 (23rd,
Hong Kong) snapshot read on 2026-07-09 (see resources/official-source-map.md) and the successor may
differ (SenSys 2026 posted full 12 / short 6 pages).
Pick the track before the PDF
- IP track (Information Processing): algorithms, estimation, signal processing, inference, learning, localization. Reviewed by method reviewers who check soundness, baselines, and whether the information-processing claim holds.
- SPOTS track (Sensor Platforms, Tools and Design Methods): hardware, embedded software, tools, measurement, deployments. Reviewed for reusability, measured design trade-offs, and real-system evidence.
A mis-tracked paper draws the wrong reviewers and loses on the wrong axis. Confirm whether the successor keeps this split or uses a single track with categories (待核实).
Format and page budget
- ACM Primary Article Template, unmodified, two-column, 9 pt (IPSN 2024). This is a compact two-column budget — not FSE's generous single-column journal budget; do not carry that habit over.
- Page budget (verify per cycle): IPSN 2024 posted ≤12 pages inclusive of figures, tables, and references — there is no separate reference allowance. SenSys 2026 posted 12 (full) / 6 (short). Everything a reviewer must read to judge the paper lives inside the budget.
- Margins, font, and column layout are fixed by the template; editorial compression, not template tampering, recovers space.
Double-blind sweep (hardware papers leak in unusual places)
IPSN is double-blind. Sensor-systems papers leak identity through hardware and deployment artifacts more than software papers do:
# Mechanical pass on the submission PDF and any anonymized artifact archive
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|doi\.org|acknowledg|grant|university|@[a-z0-9.]+\.edu' | head
unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/|firmware.*owner' | headThe IPSN-specific leaks to hunt by eye:
- Board photos and PCB silkscreen showing a lab logo, university name, or a distinctive bench.
- Oscilloscope / logic-analyzer screenshots with a captured hostname or lab watermark.
- Testbed and building names ("our 4th-floor CS testbed", a named bridge or campus) that identify the institution.
- Firmware repo owners, dataset DOIs, and IEEE DataPort links that resolve to an author.
- Deployment site coordinates or photos that pinpoint an author's city or institution.
Re-host datasets and firmware behind an anonymizing archive before upload, and blur or crop identifying hardware imagery.
Dataset and artifact at submission
- Provide an anonymized dataset/firmware link or archive, and state what will be released after acceptance. IPSN's artifact and Best Research Artifact culture makes a missing release story a scored weakness, not a neutral choice.
- Log energy/latency measurement conditions and ground truth now; these cannot be reconstructed at review time.
Show full SKILL.md (285 more words)Show less
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Main text over the page budget | Desk-reject-grade | Cut or move to the artifact; there is no separate reference allowance in the 12-page inclusive budget |
| Template altered (margins, shrunk font, single-column) | Named desk-reject ground | Recompile clean on the ACM template, recover space editorially |
| Identity leak in PDF, board photo, testbed name, or dataset link | Anonymity violation (desk-reject risk) | Re-anonymize imagery and re-host artifacts; scrub PDF metadata |
| Wrong track (platform paper in IP, or estimator in SPOTS) | Reviewer mismatch | Re-file under the matching track before the deadline |
| No dataset/firmware release story | Scored against the paper | Add an anonymized package + a release statement |
| Same work under review elsewhere | Dual-submission exposure | Withdraw one venue; verify the current concurrent-submission wording |
Final-week order of operations
- Confirm the live successor (SenSys) call, its deadline, and whether the track split survives.
- Freeze the body early; measurements and figures can be re-plotted, the argument cannot.
- Register title/abstract/authors/conflicts and pick the track before the cutoff.
- Build the anonymized dataset/firmware package and place its link and release statement in the paper.
- Run the mechanical anonymity checks on the final PDF and archive, plus an eyes-on pass over every board photo, scope screenshot, and testbed name.
- Fill every HotCRP field — topic tags matching your track, conflicts for every coauthor's institution and recent collaborators — a day early.
- Re-download the uploaded PDF and read it cold.
Reverify each cycle
- That the venue is the current SenSys edition at CPS-IoT Week (IPSN does not run standalone).
- Track structure (IP/SPOTS vs single track), the page budget, and the ACM template revision.
- Rebuttal mechanics, dual-submission wording, artifact/award timing, and any AI-disclosure rule — all cycle-volatile.
Output format
[IPSN/SenSys submission status] ready / blocked / needs work
[Track] IP / SPOTS (or successor category), matches the primary novelty? yes/no
[Format] pages used, ACM template compliance (two-column 9 pt)
[Anonymity] clean / leaks: <PDF metadata | board photo | testbed name | dataset link>
[Dataset/artifact] anonymized link present? release statement present?
[Fix queue] <ordered, with owners and dates before the AoE cutoff>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ipsn Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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 | |
| Mirrord Operatormetalbear-co/mirrord | 5.4k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence |
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.
Mirrord Operator
metalbear-co/mirrord
Help users install and configure the mirrord Operator for team/enterprise environments.
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.
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 Submission
What does Ipsn Submission do?
A skill your agent uses when auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the…. Ipsn Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the double-blind sweep for hardware/deployment papers, dataset/artifact links, and desk-reject triage — routed to the current successor (SenSys) call because IPSN no longer runs standalone.
When should I use Ipsn Submission?
Ipsn Submission fits situations like: auditing an IPSN-lineage submission for HotCRP readiness; covering the IP-vs-SPOTS track choice; the ACM Primary Article Template and ≤12-page inclusive budget; the double-blind sweep for hardware/deployment papers.
How do I install Ipsn Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-submission -a claude-code`. Or copy the skill folder (IPSN-Skills/skills/ipsn-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ipsn-submission in your project. Claude Code loads it when a task matches its description.
How do I install Ipsn Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-submission -a codex`. Or copy the skill folder (IPSN-Skills/skills/ipsn-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ipsn-submission in your project. Codex loads it when a task matches its description.
Can I use Ipsn Submission 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-submission -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-submission, .gemini/skills/ipsn-submission, .github/skills/ipsn-submission and .opencode/skills/ipsn-submission in your project.
What does Ipsn Submission need to run?
Going by SKILL.md and its folder, Ipsn Submission needs the command-line tools its instructions call (pdftotext).
Does Ipsn Submission 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 Submission 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 Submission use?
Ipsn Submission 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 Submission use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Submission?
Skills that share tags, products or a category with Ipsn Submission: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Mirrord Operator (metalbear-co/mirrord, 5.4k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ipsn Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.