Persona Customer Support
googleworkspace/cli
Manage customer support — track tickets, respond, escalate issues.
A skill your agent uses when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited…
MITAuto-check passed
Install Micro Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-supplementary --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/MICRO-Skills/skills/micro-supplementary .claude/skills/micro-supplementary && 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 "micro-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-supplementary into .claude/skills/micro-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-supplementary", 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/MICRO-Skills/skills/micro-supplementaryType 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 micro-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-supplementary --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/MICRO-Skills/skills/micro-supplementary .agents/skills/micro-supplementary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "micro-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-supplementary into .agents/skills/micro-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-supplementary", 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 micro-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-supplementary --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/MICRO-Skills/skills/micro-supplementary .cursor/skills/micro-supplementary && 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 "micro-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-supplementary into .cursor/skills/micro-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-supplementary", 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 MICRO-Skills/skills/micro-supplementary--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 micro-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-supplementary --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/MICRO-Skills/skills/micro-supplementary .gemini/skills/micro-supplementary && 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 "micro-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-supplementary into .gemini/skills/micro-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-supplementary", 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 micro-supplementaryInstalls 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 micro-supplementary -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/MICRO-Skills/skills/micro-supplementary .github/skills/micro-supplementary && 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 "micro-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-supplementary into .github/skills/micro-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-supplementary", 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 micro-supplementary -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 micro-supplementary --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/MICRO-Skills/skills/micro-supplementary .opencode/skills/micro-supplementary && 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 "micro-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-supplementary into .opencode/skills/micro-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-supplementary", 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
micro-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 755 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited…
- Works in 2 steps: Nothing decision-critical may live… → The link itself is regulated. Artifact…
- Deciding where a MICRO papers supporting material lives
- SKILL.md covers The four legal destinations, Triage procedure for…, What the artifact repo should… and Reviewer psychology around the…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Micro Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited references, an anonymized artifact repository, or the post-acceptance two-page artifact appendix, and cutting what fits nowhere.
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 where a MICRO papers supporting material lives
- Because MICRO allows no appendix at all — triaging content into the 11 reviewed pages
- The unlimited references
- An anonymized artifact repository
Example prompts
- “/micro-supplementary”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Nothing decision-critical may live outside the 11 pages. Reviewers are not
- The link itself is regulated. Artifact links must be fully anonymized or
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
Micro Supplementary loads about 1.6k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 755 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). 755 words, ~1,621 tokens.
Download SKILL.mdSave it as
.claude/skills/micro-supplementary/SKILL.md (or your agent's skills folder).- name
- micro-supplementary
- description
- Use when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited references, an anonymized artifact repository, or the post-acceptance two-page artifact appendix, and cutting what fits nowhere.
MICRO Supplementary Material
Most conference packs teach how to organize an appendix. MICRO needs the opposite skill: the 2026 submission guidelines allow 11 content pages, unlimited references, and no appendix whatsoever. There is no supplementary PDF upload and no "reviewers may optionally read" tier. Everything either earns a place in the 11 pages, moves to an artifact repository, or gets cut. This skill is the triage.
The four legal destinations
| Destination | Review status | What belongs there |
|---|---|---|
| 11 content pages | Reviewed, binding | Anything a reviewer needs to judge correctness or significance |
| References (unlimited) | Reviewed | Full citation record — every entry with all authors named, no "et al." |
| Anonymized artifact repo (linked) | Not owed a read | Configs, raw stats, extra sweeps, trace recipes, proofs of side claims |
| Camera-ready artifact appendix (≤ 2 pages, post-AE, 2025 pattern) | Post-acceptance only | How to reproduce — hardware/software requirements, run steps |
Two consequences follow immediately:
- Nothing decision-critical may live outside the 11 pages. Reviewers are not obligated to open the artifact link, and many will not while anonymous. If the security argument, the key ablation, or the storage accounting is only in the repo, the paper is incomplete as reviewed.
- The link itself is regulated. Artifact links must be fully anonymized or removed (2026 guidelines). An anonymized repo (e.g., an anonymous hosting service) is legal; a lab GitHub URL is a desk-level anonymity violation.
Triage procedure for over-length drafts
When the draft is at 13 pages and the venue gives you 11:
- Classify every subsection as
judge(reviewer needs it to score the paper),trust(supports a claim but a summary sentence + repo pointer suffices), ornice(context, extra results, alternate configs). judgestays, compressed: convert prose methodology into the config table, merge redundant ablation figures, tighten the walkthrough.trustbecomes one sentence with a forward pointer: "the full 48-workload sweep (repo,sweeps/) matches the subset shown."niceis deleted. Not moved — deleted. MICRO gives it nowhere to go, and "omitted for space" phrasing signals the cut poorly (seemicro-writing-style).
triage ledger (keep in the repo, not the paper)
------------------------------------------------
S4.3 replacement-policy interaction judge compress to half column
S5.6 per-benchmark IPC traces trust 1 sentence + repo path stats/traces/
S5.7 alternate 14nm power results nice cut; keep runnable in repo
S6.2 sensitivity beyond 8 cores trust fold into Fig. 9 right panelWhat the artifact repo should contain at submission time
Even though nobody owes it a read, a well-stocked anonymous repo pays twice — some reviewers do open it, and it becomes the AE package with zero rework in August:
- Run manifests + raw statistics for every figure (see
micro-reproducibility). - Simulator patches and full config files for baseline, mechanism, and ablations.
- Trace-generation recipes (not the traces themselves if licensing forbids — SPEC binaries cannot be redistributed; scripts and flags can).
- A top-level README with a figure-to-directory map, scrubbed of identity.
Show full SKILL.md (333 more words)Show less
Reviewer psychology around the link
Assume three reader types and satisfy all three:
- Never opens the repo (the majority while anonymous). The 11 pages must carry the full argument — this reader is the reason nothing decision-critical leaves the body.
- Opens it to spot-check one claim that bothered them. The figure-to-data map in the README decides whether this visit builds or burns trust; a maze of undocumented directories reads as concealment.
- Opens it forensically — a methodology-minded reviewer diffing your configs against the paper's tables. Config files that contradict the methodology section are worse than no link at all; regenerate both from one source.
If institutional or licensing constraints forbid sharing anything at submission time, say so in the paper in one neutral sentence and rest the case entirely on the 11 pages — a missing link is survivable, a broken or identity-leaking one is not.
Camera-ready appendix (the one appendix MICRO permits)
After acceptance and successful artifact evaluation, MICRO's recent cycles (2025 verified; 2026 待核实) let authors add a two-page artifact appendix, free of charge, describing requirements and reproduction steps. Draft it from the repo README — it is the only place appendix-style material ever reaches the PDF, and it arrives at camera-ready, not submission.
Compression techniques that reclaim body space honestly
Before cutting judge-class content, reclaim space that formatting rules allow:
- Convert methodology prose into the config table — a half-page paragraph usually compresses to six table rows with zero information loss.
- Merge single-question figures: two ablation bar charts sharing an x-axis become one two-panel figure with one caption.
- Replace repeated config descriptions with a named-config shorthand defined once ("cfg-A = Table 2 plus 16 cores").
- Prune the intro's second background paragraph — at MICRO the audience arrives knowing what a cache is; the characterization data is the background.
What never gets compressed away: the storage-budget table, the overhead rows, the sampling recipe, and the worst-case regression sentence — cutting any of those to fit is trading a format problem for a review problem.
Output format
[Appendix check] draft contains appendix material: none / found (list — must be cleared)
[Triage] judge: <sections> · trust: <sections + pointer sentences drafted> · nice: <cut list>
[Page result] content pages after triage: N/11
[Repo] anonymized: yes / no · figure-to-data map complete: yes / no
[Link policy] every artifact link anonymized-or-removed: confirmed / violations
[AE seed] repo doubles as artifact package: ready / gaps listed© 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 MICRO-Skills/skills/micro-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Micro Supplementary 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 |
|---|---|---|---|---|---|---|
| Micro Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Persona Customer Supportgoogleworkspace/cli | 31k | — | ~303 | Automated safety check: Pass | Apache-2.0 | |
| Customer Support Agentmastra-ai/mastra | 29k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Setting Up Support Slack LocallyPostHog/posthog | 40k | — | ~2.3k | Automated safety check: Notes | Custom licence | |
| Triaging Web Analytics SupportPostHog/posthog | 40k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Triage Support Bundlenetdata/netdata | 81k | — | ~2.7k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Customer Support Agent
mastra-ai/mastra
Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues.
- Official
Setting Up Support Slack Locally
PostHog/posthog
Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back.
- Official
Triaging Web Analytics Support
PostHog/posthog
Triage web analytics support tickets end to end: enumerate open tickets from the in-app conversations product and their Zendesk mirrors, classify each into a diagnostic shape (frontend crash, "two…
Triage Support Bundle
netdata/netdata
Investigate a Netdata support bundle offline - the archive netdata-support-bundle produces - to explain one host's alerts, missing data, collector failures, crashes, high CPU or memory, streaming…
Investor Materials
affaan-m/ECC
创建和更新宣传文稿、一页简介、投资者备忘录、加速器申请、财务模型和融资材料。当用户需要面向投资者的文件、预测、资金用途表、里程碑计划或必须在多个融资资产中保持内部一致性的材料时使用。
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 Micro Supplementary
What does Micro Supplementary do?
A skill your agent uses when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited…. Micro Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited references, an anonymized artifact repository, or the post-acceptance two-page artifact appendix, and cutting what fits nowhere.
When should I use Micro Supplementary?
Micro Supplementary fits situations like: deciding where a MICRO papers supporting material lives; because MICRO allows no appendix at all — triaging content into the 11 reviewed pages; the unlimited references; an anonymized artifact repository.
How do I install Micro Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-supplementary -a claude-code`. Or copy the skill folder (MICRO-Skills/skills/micro-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/micro-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Micro Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-supplementary -a codex`. Or copy the skill folder (MICRO-Skills/skills/micro-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/micro-supplementary in your project. Codex loads it when a task matches its description.
Can I use Micro Supplementary 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 micro-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/micro-supplementary, .gemini/skills/micro-supplementary, .github/skills/micro-supplementary and .opencode/skills/micro-supplementary in your project.
What does Micro Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Micro Supplementary is instructions for the agent only.
Does Micro Supplementary 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 Micro Supplementary 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 Micro Supplementary use?
Micro Supplementary 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 Micro Supplementary 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 Micro Supplementary?
Skills that share tags, products or a category with Micro Supplementary: Persona Customer Support (googleworkspace/cli, 31k stars), Customer Support Agent (mastra-ai/mastra, 29k stars), Setting Up Support Slack Locally (PostHog/posthog, 40k stars) and Triaging Web Analytics Support (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Micro Supplementary?
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.