Embeddings
ruvnet/ruflo
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support.
A skill your agent uses when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and…
MITAuto-check passed
Install Ipsn Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-topic-selection --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-topic-selection .claude/skills/ipsn-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-topic-selection into .claude/skills/ipsn-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-topic-selection", 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-topic-selectionType 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-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-topic-selection --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-topic-selection .agents/skills/ipsn-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-topic-selection into .agents/skills/ipsn-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-topic-selection", 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-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-topic-selection --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-topic-selection .cursor/skills/ipsn-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-topic-selection into .cursor/skills/ipsn-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-topic-selection", 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-topic-selection--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-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-topic-selection --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-topic-selection .gemini/skills/ipsn-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-topic-selection into .gemini/skills/ipsn-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-topic-selection", 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-topic-selectionInstalls 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-topic-selection -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-topic-selection .github/skills/ipsn-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-topic-selection into .github/skills/ipsn-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-topic-selection", 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-topic-selection -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-topic-selection --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-topic-selection .opencode/skills/ipsn-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-topic-selection into .opencode/skills/ipsn-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-topic-selection", 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-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 707 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and…
- Deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution
- SKILL.md covers First decision: IP track or…, Second decision: is this the…, The merger reality (do not skip) and The model-swap and…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A Sensor Platforms
What it does
Ipsn Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and whether it should go to the IPSN lineage (now the merged SenSys at CPS-IoT Week), a CPS-IoT Week neighbor (RTAS/ICCPS/HSCC), MobiSys/MobiCom, INFOCOM, or a signal-processing journal.
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.
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
- Deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution
- A Sensor Platforms
- Tools and Design Methods (SPOTS) contribution
- Whether it should go to the IPSN lineage (now the merged SenSys at CPS-IoT Week)
Example prompts
- “/ipsn-topic-selection”
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 Topic Selection loads about 1.6k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 707 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). 707 words, ~1,629 tokens.
Download SKILL.mdSave it as
.claude/skills/ipsn-topic-selection/SKILL.md (or your agent's skills folder).- name
- ipsn-topic-selection
- description
- Use when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and whether it should go to the IPSN lineage (now the merged SenSys at CPS-IoT Week), a CPS-IoT Week neighbor (RTAS/ICCPS/HSCC), MobiSys/MobiCom, INFOCOM, or a signal-processing journal.
IPSN Topic Selection
Decide two things before drafting: which track and which venue. IPSN — the ACM/IEEE International Conference on Information Processing in Sensor Networks — split its research papers into the Information Processing (IP) track and the Sensor Platforms, Tools and Design Methods (SPOTS) track, and it lived inside CPS-IoT Week. As of 2026-07-09 IPSN no longer runs standalone — it merged into SenSys (Embedded AI and Sensing Systems) — but the IP-vs-SPOTS instinct still decides how your paper is read and where its evidence bar sits, so keep it.
First decision: IP track or SPOTS track
This is the choice with no sibling analogue. Get it wrong and your platform paper is judged by theory reviewers, or your estimator is judged by hardware reviewers.
| Signal in your project | Track | Why |
|---|---|---|
| The core is an algorithm, estimator, inference, or learning method for sensed data | IP | Information processing is the contribution; energy/error/bits are the currency |
| Localization, tracking, sensor fusion, compressive sensing, on-device/TinyML inference | IP | These are IP-track staples; the platform is a vehicle, not the point |
| The core is a new device, mote, radio front-end, or embedded-software/tool advance | SPOTS | Sensor Platforms, Tools and Design Methods is its named home |
| A real deployment whose lesson is about building/operating the system | SPOTS (often) | Yield, synchronization, robustness, and design methods dominate |
| A dataset/measurement study of a sensing modality | Either — decide by whether the method or the platform/measurement is new | The track is chosen by where the novelty lives |
Rule of thumb from IPSN's own wording: analysis and processing of collected data → IP; hardware/software platforms and tools used to collect it → SPOTS. A paper with both a new estimator and a new board picks the track matching its primary claim and treats the other as support.
Second decision: is this the IPSN lineage at all?
IPSN rewards work where information processing meets physical sensing. A pure ML result with a sensing dataset, or a pure networking result, is respected and then rerouted.
| Your project's center of gravity | Better home | Why |
|---|---|---|
| Sensing algorithm/inference/localization with a real-hardware or energy consequence | IPSN lineage → SenSys (IP track) | The information-processing-meets-sensing core |
| A sensor platform, tool, or deployment with measured design trade-offs | IPSN lineage → SenSys (SPOTS track) | The platform/tools core |
| Hard real-time scheduling or timing guarantees | RTAS | CPS-IoT Week neighbor; real-time systems is its center |
| Hybrid/control-theoretic CPS, verification, or autonomy | HSCC / ICCPS | CPS-IoT Week neighbors; control and hybrid systems |
| Mobile/wearable/smartphone sensing systems, human-in-the-loop | MobiSys / MobiCom / UbiComp | Mobile-computing communities, different reviewer pool |
| Wireless protocol/throughput/network-measurement result | INFOCOM / NSDI / MobiCom | Networking venues |
| A deep estimation/signal-processing result with no systems payoff | IEEE TSP / SPAWC / a SP journal | Signal-processing home; IPSN wants the sensing consequence |
Show full SKILL.md (271 more words)Show less
The merger reality (do not skip)
IPSN's last standalone edition was IPSN 2024 (23rd, Hong Kong). From 2025 it merged with SenSys and IoTDI; the live venue is SenSys — Embedded AI and Sensing Systems, still at CPS-IoT Week. Practical consequences:
- "Submit to IPSN" now means submit to SenSys with an IP-track or SPOTS-track style of contribution. Confirm on the current SenSys call whether it keeps an explicit track split or folds it into one technical track with categories (待核实).
- Do not send authors to an archived
ipsn.acm.org/2026— no such standalone conference exists.
The model-swap and platform-swap tests
- Model-swap test (IP track): if your paper leans on a specific learner/model, ask whether the sensing lesson survives swapping it. If not, the model is the contribution and an ML venue fits better; if yes, it is an IP-track sensing result.
- Platform-swap test (SPOTS track): would your platform/tool contribution still matter on a different application? If it only helps your one demo, it is an application paper, not a SPOTS contribution.
Evidence maturity, without the ladder cliché
Fit is necessary but not sufficient. An estimator with a bound but no real-sensor evaluation is a theory note; a board with a datasheet but no measured power/robustness story is an engineering report; a deployment with no ground truth is an anecdote. IPSN wants the information-processing claim and the physical measurement that makes it real.
Cheap reconnaissance before committing
[Scope] scan recent IPSN (dblp, ACM DL/IEEE Xplore) and the latest SenSys program for your subarea
-> 3+ recent papers = a reviewer pool exists; 0 = mismatch or reroute
[Track] is your novelty in the method (IP) or the platform/tools/deployment (SPOTS)?
[Citations] is your bibliography majority sensing venues (IPSN/SenSys/MobiCom/INFOCOM + SP)?
-> majority pure-ML or pure-networking => reviewers read you as a visitor; reframe first
[Calendar] the live target is the next SenSys edition at CPS-IoT Week -> confirm its deadlineDecision procedure
[Who acts] who changes behavior if the claim holds? sensor-system builders / deployers / SP researchers?
[Claim type] estimator/inference (IP) / platform/tool/deployment (SPOTS)
[Track] IP vs SPOTS, chosen by where the primary novelty lives
[Venue] IPSN-lineage (SenSys) / RTAS / HSCC-ICCPS / MobiSys-MobiCom / INFOCOM / SP journal
[Verdict] track + venue, with a one-line reason and the live successor deadline to confirmRun this before the writing skills; a wrong track or venue wastes every later step. When the verdict
is the IPSN lineage, continue with ipsn-workflow for the CPS-IoT Week calendar and
ipsn-writing-style for the paper shape.
© 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-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ipsn Topic Selection 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 Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Embeddingsruvnet/ruflo | 74k | 3 repos | ~455 | Automated safety check: Pass | MIT | |
| Embedding Strategieswshobson/agents | 40k | 11 repos | ~710 | Automated safety check: Pass | MIT | |
| Embeddings via 9Routerdecolua/9router | 30k | — | ~604 | Automated safety check: Pass | MIT | |
| Embeddingsalsk1992/CloddsBot | 2.9k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Embedded Iot Mentoralirezarezvani/claude-skills | 28k | — | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Embedding Strategies
wshobson/agents
Helps choose and tune embedding models for semantic search and RAG: model comparison, chunking, preprocessing, normalization and caching.
Embeddings via 9Router
decolua/9router
Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.
Embeddings
alsk1992/CloddsBot
Vector embeddings configuration and semantic search. An agent skill from alsk1992/CloddsBot.
Embedded Iot Mentor
alirezarezvani/claude-skills
Mentor for embedded and IoT hardware projects. An agent skill from alirezarezvani/claude-skills.
Photopea Embedded Editor
sickn33/agentic-awesome-skills
Embed Photopea in web apps using photopea.js. An agent skill from sickn33/agentic-awesome-skills.
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…
Questions about Ipsn Topic Selection
What does Ipsn Topic Selection do?
A skill your agent uses when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and…. Ipsn Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and whether it should go to the IPSN lineage (now the merged SenSys at CPS-IoT Week), a CPS-IoT Week neighbor (RTAS/ICCPS/HSCC), MobiSys/MobiCom, INFOCOM, or a signal-processing journal.
When should I use Ipsn Topic Selection?
Ipsn Topic Selection fits situations like: deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution; A Sensor Platforms; tools and Design Methods (SPOTS) contribution; whether it should go to the IPSN lineage (now the merged SenSys at CPS-IoT Week).
How do I install Ipsn Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-topic-selection -a claude-code`. Or copy the skill folder (IPSN-Skills/skills/ipsn-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ipsn-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Ipsn Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-topic-selection -a codex`. Or copy the skill folder (IPSN-Skills/skills/ipsn-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ipsn-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Ipsn Topic Selection 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-topic-selection -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-topic-selection, .gemini/skills/ipsn-topic-selection, .github/skills/ipsn-topic-selection and .opencode/skills/ipsn-topic-selection in your project.
What does Ipsn Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Ipsn Topic Selection is instructions for the agent only.
Does Ipsn Topic Selection 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 Topic Selection 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 Topic Selection use?
Ipsn Topic Selection 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 Topic Selection use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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 Topic Selection?
Skills that share tags, products or a category with Ipsn Topic Selection: Embeddings (ruvnet/ruflo, 74k stars), Embedding Strategies (wshobson/agents, 40k stars), Embeddings via 9Router (decolua/9router, 30k stars) and Embeddings (alsk1992/CloddsBot, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ipsn Topic Selection?
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.