Longbridge Research
helsome/folio
Institution ratings, consensus price targets, EPS/revenue forecasts, finance calendar, shareholder data, fund holders, insider trades (SEC Form 4), short interest, industry rankings, peer group…
A skill your agent uses when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising…
Install Uist Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-author-response .claude/skills/uist-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 "uist-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-author-response into .claude/skills/uist-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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/UIST-Skills/skills/uist-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 uist-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-author-response .agents/skills/uist-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 "uist-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-author-response into .agents/skills/uist-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-author-response .cursor/skills/uist-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 "uist-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-author-response into .cursor/skills/uist-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 UIST-Skills/skills/uist-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 uist-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-author-response .gemini/skills/uist-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 "uist-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-author-response into .gemini/skills/uist-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-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 uist-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/UIST-Skills/skills/uist-author-response .github/skills/uist-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 "uist-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-author-response into .github/skills/uist-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-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 uist-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/UIST-Skills/skills/uist-author-response .opencode/skills/uist-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 "uist-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-author-response into .opencode/skills/uist-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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
uist-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 589 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising…
- Writing the UIST rebuttal — budgeting the 5
- SKILL.md covers Budgeting 5,000 characters, Structure that survives skimming, A point, done badly and well and Working the window, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- 000-character self-contained response
What it does
Uist Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising only camera-ready changes you can deliver, and writing for the PC discussion that follows rather than for the reviewers alone.
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 Business, Finance & HR, covering Budgeting and forecasting. 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
- Writing the UIST rebuttal — budgeting the 5
- 000-character self-contained response
- Prioritizing factual corrections and novelty defenses over taste disputes
- Promising only camera-ready changes you can deliver
Example prompts
- “/uist-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
Uist Author Response loads about 1.6k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 589 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). 589 words, ~1,569 tokens.
Download SKILL.mdSave it as
.claude/skills/uist-author-response/SKILL.md (or your agent's skills folder).- name
- uist-author-response
- description
- Use when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising only camera-ready changes you can deliver, and writing for the PC discussion that follows rather than for the reviewers alone.
UIST Author Response
The UIST rebuttal is small, plain-text, and consequential: 5,000 characters, self-contained, written in about a week (May 28 - June 5 in the verified 2026 cycle), and explicitly listed among the inputs to the accept/reject recommendation. Its second life matters more than its first: because acceptances are conditional on "changes described in the rebuttal," this document becomes the contract for your camera-ready. Draft it as both an argument and a promise you must keep by July 24.
Budgeting 5,000 characters
That is roughly 700-800 words — three to five points argued well. Spend by expected value, not by emotional temperature:
| Priority | Point type | Why it pays |
|---|---|---|
| 1 | Factual error in a review | Cheap to correct, moves discussion immediately |
| 2 | Novelty challenge ("X does this") | A capability-delta answer can flip a score |
| 3 | Direct reviewer questions | Unanswered questions read as concessions |
| 4 | Evidence gap where evidence exists | Report the number; it was measured, not new |
| 5 | Scope concession | Narrowing a claim can defuse a rejection rationale |
| — | Taste disagreements | Skip; acknowledge in one clause if at all |
Self-contained means the committee should not need to re-open the paper to follow your point — quote the review's phrase, state the fact, cite section and figure by number.
Structure that survives skimming
The PC meeting skims. Number everything and front-load the verdict of each point:
We thank the reviewers. We address the main concerns within the limit.
[R1-novelty] R1 notes SystemX "achieves the same interaction." SystemX
localizes touch at 4 discrete sites (their Sec 5); ours is continuous 2D
(±2.1 mm, Sec 6.2, Fig 7). We will add this comparison to Table 2.
[R2-latency] R2 asks for end-to-end latency. Measured: 11.3 ms median,
18.9 ms p95 over 10k events (harness in supplement). We will surface this
in Sec 6.1, currently appendix-only.
[R1,R3-study scope] We agree the 12-person study supports only the
large-effect comparison; we will narrow the claim in Sec 7 accordingly.Conventions: tag each point with reviewer + topic; state fact before promise; make every promise concrete and located ("add to Table 2"), because vague promises are uncheckable conditions and specific ones become your camera-ready checklist.
A point, done badly and well
Same objection, two treatments — the difference is fact-density per character:
BAD (defensive, 490 chars, no facts):
We respectfully disagree with R2's characterization of our latency. The
reviewer may have overlooked the appendix, where this was discussed. Our
system is highly optimized and latency was never an issue in practice, as
any user of the system can confirm. We believe this concern does not
affect the contribution of the paper, which R1 and R3 both appreciated.
GOOD (factual, 330 chars, promise included):
[R2-latency] Measured end-to-end: 11.3 ms median, 18.9 ms p95 over 10k
events (App. C, harness in supplement). This is below the 20 ms
perceptibility threshold R2 cites. We will move the measurement from
App. C into Sec 6.1 and state the boundary conditions there.The bad version spends characters on feelings and reviewer psychology; the good version spends them on numbers, locations, and one checkable promise.
Working the window
The 2026 window was eight days (May 28 - June 5). A schedule that survives it:
- Day 1: all authors read all reviews cold, separately; bins assigned independently, then merged — solo triage under-weights whichever reviewer annoyed the lead author.
- Days 2-3: hunt existing evidence for every evidence-gap point (logs, pilot data, appendix numbers reviewers missed); draft the promise ledger.
- Days 4-5: full draft, over budget; cut to 5,000 characters by deleting points, not by compressing sentences into unreadability.
- Day 6: cold read by a non-author; tone and self-containedness check.
- Day 7: submit. Never the final day — the window does not extend.
Show full SKILL.md (193 more words)Show less
What a rebuttal cannot do
- No new experiments as argument. Reporting an existing measurement reviewers missed is fair; describing studies you would run is a promise reviewers are told to discount.
- No links, no attachments. Self-contained plain text; a URL is both a rule violation and an anonymity hazard.
- No hostility, no meta-complaints about reviewer quality — the discussion phase that follows is among exactly those people, and your tone is data about what you'd be like as a colleague in a small single-track community.
Deciding whether to rebut at all
Rebuttal is optional. Skip it only when reviews are uniformly positive with no questions, or uniformly negative on grounds that are true. Anything mixed gets a response: the 2026 process wording makes the rebuttal part of the record the PC discusses, and silence leaves reviewer errors standing as facts.
The promise ledger
Before submitting, extract every "we will..." into a ledger with a cost estimate. The +10% camera-ready allowance (one page standard / half page short in 2026) is the hard budget for delivering them:
PROMISE COST FITS +10%?
Comparison row for SystemX 3 lines yes
Latency table to Sec 6.1 0.2 pp yes
Narrowed claim in Sec 7 rewrite yes
"Additional participants" weeks NO — do not promiseOver-promising creates a conditional acceptance you cannot satisfy; under-promising leaves reviewer concerns unaddressed. Promise exactly what fits.
Output format
[Rebuttal plan] <points in order, each: reviewer-tag, fact, promise>
[Character budget] <estimated / 5000>
[Skipped points] <taste/unwinnable items deliberately dropped>
[Promise ledger] <each promise + cost + fits-allowance verdict>
[Tone check] performed by <non-author reader>© 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 UIST-Skills/skills/uist-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uist 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 |
|---|---|---|---|---|---|---|
| Uist Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Longbridge Researchhelsome/folio | 271 | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Bet SizingJoelLewis/finance_skills | 206 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Cre Asset Managementahacker-1/cre-agent-skills | 113 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Dd LogsDataDog/pup | 1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Cash Flow ForecastWellApp-ai/Well | 345 | — | ~567 | Automated safety check: Pass | MIT |
Similar skills
Bet Sizing
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
Cre Asset Management
ahacker-1/cre-agent-skills
CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions…
- Official
Dd Logs
DataDog/pup
Log management - search, pipelines, archives, and cost control.
Cash Flow Forecast
WellApp-ai/Well
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions.
Cash Flow Snapshot
sandbaseai/sandbase-skills
Create a 30/60/90-day cash-flow forecast from AR, AP, opening cash, payment timing, and fixed-cost data.
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 Uist Author Response
What does Uist Author Response do?
A skill your agent uses when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising…. Uist Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising only camera-ready changes you can deliver, and writing for the PC discussion that follows rather than for the reviewers alone.
When should I use Uist Author Response?
Uist Author Response fits situations like: writing the UIST rebuttal — budgeting the 5; 000-character self-contained response; prioritizing factual corrections and novelty defenses over taste disputes; promising only camera-ready changes you can deliver.
How do I install Uist Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-author-response -a claude-code`. Or copy the skill folder (UIST-Skills/skills/uist-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uist-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Uist Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-author-response -a codex`. Or copy the skill folder (UIST-Skills/skills/uist-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uist-author-response in your project. Codex loads it when a task matches its description.
Can I use Uist 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 uist-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/uist-author-response, .gemini/skills/uist-author-response, .github/skills/uist-author-response and .opencode/skills/uist-author-response in your project.
What does Uist Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Uist Author Response is instructions for the agent only.
Does Uist 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 Uist 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 Uist Author Response use?
Uist 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 Uist Author Response use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Uist Author Response?
Skills that share tags, products or a category with Uist Author Response: Longbridge Research (helsome/folio, 271 stars), Bet Sizing (JoelLewis/finance_skills, 206 stars), Cre Asset Management (ahacker-1/cre-agent-skills, 113 stars) and Dd Logs (DataDog/pup, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uist 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.