Sync Upstream
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
A skill your agent uses when drafting an IPSN-lineage rebuttal, covering the double-blind response to sensor-systems reviewers on ground truth, baseline fairness, deployment realism, energy…
Install Ipsn Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-author-response --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-author-response .claude/skills/ipsn-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-author-response into .claude/skills/ipsn-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-author-response", 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-author-responseType 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-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-author-response --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-author-response .agents/skills/ipsn-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-author-response into .agents/skills/ipsn-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-author-response", 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-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-author-response --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-author-response .cursor/skills/ipsn-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-author-response into .cursor/skills/ipsn-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-author-response", 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-author-response--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-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-author-response --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-author-response .gemini/skills/ipsn-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-author-response into .gemini/skills/ipsn-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-author-response", 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-author-responseInstalls 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-author-response -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-author-response .github/skills/ipsn-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-author-response into .github/skills/ipsn-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-author-response", 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-author-response -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-author-response --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-author-response .opencode/skills/ipsn-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-author-response into .opencode/skills/ipsn-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-author-response", 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-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 470 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting an IPSN-lineage rebuttal, covering the double-blind response to sensor-systems reviewers on ground truth, baseline fairness, deployment realism, energy…
- Drafting an IPSN-lineage rebuttal
- SKILL.md covers Triage, The rebuttal itself, Reviewer pushback patterns… and Anonymity in the rebuttal…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the double-blind response to sensor-systems reviewers on ground truth
What it does
Ipsn Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an IPSN-lineage rebuttal, covering the double-blind response to sensor-systems reviewers on ground truth, baseline fairness, deployment realism, energy accounting, and simulation-vs-real-hardware doubts, without leaking identity and without promising experiments not yet run.
Its SKILL.md is about 1.2k 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 Business, Finance & HR, covering Accounting and bookkeeping. 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
- Drafting an IPSN-lineage rebuttal
- Covering the double-blind response to sensor-systems reviewers on ground truth
- Baseline fairness
- Deployment realism
Example prompts
- “/ipsn-author-response”
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 Author Response loads about 1.2k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 470 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). 470 words, ~1,175 tokens.
Download SKILL.mdSave it as
.claude/skills/ipsn-author-response/SKILL.md (or your agent's skills folder).- name
- ipsn-author-response
- description
- Use when drafting an IPSN-lineage rebuttal, covering the double-blind response to sensor-systems reviewers on ground truth, baseline fairness, deployment realism, energy accounting, and simulation-vs-real-hardware doubts, without leaking identity and without promising experiments not yet run.
IPSN Author Response
Use this after IPSN-lineage reviews are released. IPSN is conference-style: a short, decision-focused rebuttal (verify the window and format on the current successor call), not a journal-style revise-and-resubmit letter. The rebuttal must stay double-blind — no author names, institutions, lab-named testbeds, or identity-revealing dataset/firmware links — and it must answer on the axes a sensor-systems reviewer actually raised.
Triage
- Answer what affects the decision: evidence realism (simulation vs real hardware), soundness of the method/platform, baseline fairness, ground-truth validity, deployment honesty, and energy/latency accounting.
- Use evidence that already exists or a number you can compute from data you already have — never a vague promise to run an experiment.
- Correct factual misreadings first; a reviewer who misread an energy table or a yield number is often persuadable.
- Keep every word anonymous. Do not name your board, testbed, institution, or a resolvable dataset DOI, even to strengthen a point.
The rebuttal itself
Short and decision-focused. One decision-critical point per reviewer beats an exhaustive reply. Concede what is true, correct what is misread, and point to exactly where the answer lives in the submitted paper or artifact. Do not paste large new results the reviewers cannot verify in the window.
[R1 - "simulation only"] -> Point to the real-hardware result already in §4.2 / Table 3 (measured on
the MCU), which the review may have missed; state the platform and clock.
[R2 - "baseline untuned"] -> Report the equal-condition comparison already logged; give the number and
where it lives; if a tuning was fixed, say the budget was equal and documented.
[R3 - "ground truth?"] -> Name the surveyed reference and its own error; correct the misread that the
ground truth came from the model under test.Reviewer pushback patterns (sensor-systems flavored)
| Pushback | What it signals | IPSN-ready response |
|---|---|---|
| "Only simulated / no real hardware" | Evidence-realism doubt (often fatal) | Point to the on-device/in-field result if it exists; if it truly doesn't, concede and scope the claim rather than promise it |
| "Baseline is not a real alternative / untuned" | Soundness doubt about the comparison | Report the equal-condition numbers; name the tuning budget |
| "Energy is estimated, not measured" | Accounting doubt | Point to the instrumented-rail measurement and conditions; if only estimated, say so and bound it |
| "Deployment numbers look idealized" | Honesty doubt | Report yield, sync error, and failures as measured; do not sand off the losses |
| "Ground truth is circular / weak" | Construct doubt | Name the independent reference and its error; state the residual limit |
| "Wrong track / out of scope" | Track or venue mismatch | Clarify the primary contribution's track; hard to fully fix in rebuttal |
Show full SKILL.md (132 more words)Show less
Anonymity in the rebuttal (easy to slip)
- Refer to your own prior work in the third person, as in the paper.
- Describe artifact/firmware changes without linking to an identity-revealing repository; use the anonymized location.
- Do not thank a named collaborator, funder, or facility inside the rebuttal.
- Do not paste a board photo or a dataset DOI that reveals the lab.
Calibration
- Respond to the criterion the reviewer actually raised, not the one you would rather defend.
- The PC discussion decides; write the rebuttal as evidence for an advocate, and let the measured evidence already in the paper carry the argument.
- IPSN is not a Major-Revision venue: there is usually no guaranteed second read, so a rebuttal that promises future experiments rarely helps. Confirm the current mechanics on the successor call.
Output format
[Turn] rebuttal (conference-style; confirm window/format on the current call)
[Priority issue] <reviewer concern>
[Decision dimension] evidence-realism / soundness / baseline / ground-truth / deployment-honesty / energy
[Answer] <where the answer lives in paper/artifact, or the honest concession + scope>
[Anonymity check] <no identity leak, incl. board photos / testbed names / dataset DOIs: passed/issues>© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ipsn Author Response 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 Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sync Upstreamnyaruka/phonenumbers | 1.6k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Radiology Tablehuang-sir1/radiology-skills | 1.9k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| ERPClaw ERP Controlleravansaber/erpclaw | 116 | — | ~18k | Automated safety check: Pass | GPL-3.0 | |
| Odoo Agency Fleet Reviewerpipe-org/mcp-odoo | 421 | — | ~699 | Automated safety check: Pass | MIT | |
| Beancount Closebex-co/beancount-io | 296 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Radiology Table
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
ERPClaw ERP Controller
avansaber/erpclaw
Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
Beancount Close
bex-co/beancount-io
Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…
Forward Implementation First
Vuk97/forward-implementation-first
Keeps an agent building and validating real output instead of servicing its own bookkeeping.
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 Author Response
What does Ipsn Author Response do?
A skill your agent uses when drafting an IPSN-lineage rebuttal, covering the double-blind response to sensor-systems reviewers on ground truth, baseline fairness, deployment realism, energy…. Ipsn Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an IPSN-lineage rebuttal, covering the double-blind response to sensor-systems reviewers on ground truth, baseline fairness, deployment realism, energy accounting, and simulation-vs-real-hardware doubts, without leaking identity and without promising experiments not yet run.
When should I use Ipsn Author Response?
Ipsn Author Response fits situations like: drafting an IPSN-lineage rebuttal; covering the double-blind response to sensor-systems reviewers on ground truth; baseline fairness; deployment realism.
How do I install Ipsn Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-author-response -a claude-code`. Or copy the skill folder (IPSN-Skills/skills/ipsn-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ipsn-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Ipsn Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-author-response -a codex`. Or copy the skill folder (IPSN-Skills/skills/ipsn-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ipsn-author-response in your project. Codex loads it when a task matches its description.
Can I use Ipsn Author Response 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-author-response -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-author-response, .gemini/skills/ipsn-author-response, .github/skills/ipsn-author-response and .opencode/skills/ipsn-author-response in your project.
What does Ipsn Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Ipsn Author Response is instructions for the agent only.
Does Ipsn Author Response 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 Author Response 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 Author Response use?
Ipsn Author Response 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 Author Response use?
About 1.2k tokens (SKILL.md is roughly 4.7k 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 Author Response?
Skills that share tags, products or a category with Ipsn Author Response: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars), ERPClaw ERP Controller (avansaber/erpclaw, 116 stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ipsn Author Response?
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.