Document Signing
asgeirtj/system_prompts_leaks
Review documents for signature or prepare a signing packet; verify fields and recipients while keeping sending and signing under explicit user authorization.
Gather information from pages that only load behind the user's own Chrome login, without touching anything else in their session.
Apache-2.0Auto-check passed
Install Signed In Research
$ npx skills add Porabuild/Poracode --skill signed-in-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Porabuild/Poracode signed-in-research --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/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/chrome-tools/skills/signed-in-research .claude/skills/signed-in-research && 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 "signed-in-research" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/chrome-tools/skills/signed-in-research into .claude/skills/signed-in-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signed-in-research", 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/Porabuild/Poracode/tree/master/resources/plugins/chrome-tools/skills/signed-in-researchType 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 Porabuild/Poracode --skill signed-in-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Porabuild/Poracode signed-in-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/plugins/chrome-tools/skills/signed-in-research .agents/skills/signed-in-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "signed-in-research" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/chrome-tools/skills/signed-in-research into .agents/skills/signed-in-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signed-in-research", 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 Porabuild/Poracode --skill signed-in-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Porabuild/Poracode signed-in-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/plugins/chrome-tools/skills/signed-in-research .cursor/skills/signed-in-research && 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 "signed-in-research" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/chrome-tools/skills/signed-in-research into .cursor/skills/signed-in-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signed-in-research", 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/Porabuild/Poracode.git --path resources/plugins/chrome-tools/skills/signed-in-research--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 Porabuild/Poracode --skill signed-in-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Porabuild/Poracode signed-in-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/plugins/chrome-tools/skills/signed-in-research .gemini/skills/signed-in-research && 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 "signed-in-research" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/chrome-tools/skills/signed-in-research into .gemini/skills/signed-in-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signed-in-research", 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 Porabuild/Poracode signed-in-researchInstalls 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 Porabuild/Poracode --skill signed-in-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/plugins/chrome-tools/skills/signed-in-research .github/skills/signed-in-research && 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 "signed-in-research" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/chrome-tools/skills/signed-in-research into .github/skills/signed-in-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signed-in-research", 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 Porabuild/Poracode --skill signed-in-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Porabuild/Poracode signed-in-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/plugins/chrome-tools/skills/signed-in-research .opencode/skills/signed-in-research && 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 "signed-in-research" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/chrome-tools/skills/signed-in-research into .opencode/skills/signed-in-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signed-in-research", 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
signed-in-research- GitHub stars
- 115
- Token cost
- ~489 tokens
- SKILL.md length
- 292 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Gather information from pages that only load behind the user's own Chrome login, without touching anything else in their session.
- SKILL.md covers Confirm the surface first, Reach the page, Read narrowly and Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Signed In Research is an agent skill from Porabuild/Poracode. Gather information from pages that only load behind the user's own Chrome login, without touching anything else in their session.
Its SKILL.md is about 490 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: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.
Example prompts
- “/signed-in-research”
What it can do on your machine
Read from SKILL.md and the folder at commit e56fcc8. 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
Signed In Research loads about 489 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 292 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 Porabuild/Poracode at commit e56fcc8, republished under its Apache-2.0 licence (© Porabuild). 292 words, ~489 tokens.
Download SKILL.mdSave it as
.claude/skills/signed-in-research/SKILL.md (or your agent's skills folder).- name
- signed-in-research
- description
- Gather information from pages that only load behind the user's own Chrome login, without touching anything else in their session.
Signed-in Research
The user's Chrome carries their real accounts. Use it when a page needs that login — an internal dashboard, a paywalled doc, an admin console — and read only what was asked for.
Confirm the surface first
Call chrome.status. A disconnected extension means the answer is "connect Chrome", not a silent switch to the
isolated browser, which has none of these logins.
Ask yourself whether the login is actually required. If the page is public, Poracode's own browser is the safer surface and leaves the user's session untouched.
Reach the page
Open the URL the user gave you. Attach to an existing tab with chrome.attach only when they asked you to work
in a tab they already have open — never because it happens to be authenticated already.
If the page redirects to a login wall, stop and say so. Do not attempt credentials, and do not go hunting through other tabs for a session that works.
Read narrowly
Pull the specific values, table, or passage the question needs, using chrome.snapshot or chrome.find.
Stay on the requested site. Other tabs, unrelated pages, and the user's history are not context you get to collect.
Leave cookies and storage alone unless the task genuinely requires them and Chrome data access is enabled.
Reading is safe; clicking often is not. In a signed-in console, buttons send invitations, cancel subscriptions, and delete records. Confirm before any action that writes, sends, or removes.
Report
Give the answer with the URL and page title it came from, and quote the part that carries it. Say which pages you could not reach and why — a login wall, an expired session, a permission error — instead of filling the gap from memory.
Call chrome.disable when you finish or pause for the user.
© Porabuild, Apache-2.0. 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 resources/plugins/chrome-tools/skills/signed-in-research of Porabuild/Poracode.
Open the folder on GitHubat commit e56fcc8
Compare with similar skills
Signed In Research 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 |
|---|---|---|---|---|---|---|
| Signed In Research this skillPorabuild/Poracode | 115 | — | ~489 | Automated safety check: Pass | Apache-2.0 | |
| Document Signingasgeirtj/system_prompts_leaks | 69k | — | ~1.5k | Automated safety check: Pass | CC0-1.0 | |
| Dropbox Sign AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~749 | Automated safety check: Pass | None | |
| Implementing Code Signing For Artifactsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Implementing Sigstore For Software Signingmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.2k | Automated safety check: Notes | Apache-2.0 | |
| Signed Audit Trails Recipewshobson/agents | 40k | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Dropbox Sign Automation
ComposioHQ/awesome-claude-skills
Automate Dropbox Sign tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Implementing Code Signing For Artifacts
mukul975/Anthropic-Cybersecurity-Skills
Implements code signing for build artifacts (binaries, packages, containers) using GPG, Sigstore, and platform-specific signing tools, establishing trust chains and verifying signatures in…
Implementing Sigstore For Software Signing
mukul975/Anthropic-Cybersecurity-Skills
Implements Sigstore-based software signing and verification using Cosign keyless signing, Rekor transparency log verification, and Fulcio certificate authority integration to establish cryptographic…
Signed Audit Trails Recipe
wshobson/agents
Step-by-step cookbook for setting up cryptographically signed audit trails on Claude Code tool calls.
- Official
Sign In With Google Web
google/skills
Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS / https://accounts.google.com/gsi/client) across web architectures.
More from Porabuild/Poracode
All 21 skills in this repoInteractive Testing
Porabuild/Poracode
Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.
Release Notes
Porabuild/Poracode
Write consistent, hand-written-looking changelog entries for a Poracode release.
Skill Creator Poracode
Porabuild/Poracode
Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.
App Controls
Porabuild/Poracode
Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.
Chrome Control
Porabuild/Poracode
Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.
Computer Use
Porabuild/Poracode
Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.
Questions about Signed In Research
What does Signed In Research do?
Gather information from pages that only load behind the user's own Chrome login, without touching anything else in their session. Signed In Research is an agent skill from Porabuild/Poracode. Gather information from pages that only load behind the user's own Chrome login, without touching anything else in their session.
How do I install Signed In Research in Claude Code?
Run `npx skills add Porabuild/Poracode --skill signed-in-research -a claude-code`. Or copy the skill folder (resources/plugins/chrome-tools/skills/signed-in-research in Porabuild/Poracode) into .claude/skills/signed-in-research in your project. Claude Code loads it when a task matches its description.
How do I install Signed In Research in Codex?
Run `npx skills add Porabuild/Poracode --skill signed-in-research -a codex`. Or copy the skill folder (resources/plugins/chrome-tools/skills/signed-in-research in Porabuild/Poracode) into .agents/skills/signed-in-research in your project. Codex loads it when a task matches its description.
Can I use Signed In Research 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 Porabuild/Poracode --skill signed-in-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/signed-in-research, .gemini/skills/signed-in-research, .github/skills/signed-in-research and .opencode/skills/signed-in-research in your project.
What does Signed In Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Signed In Research is instructions for the agent only.
Does Signed In Research 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 Signed In Research 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 Signed In Research use?
Signed In Research is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Signed In Research use?
About 489 tokens (SKILL.md is roughly 2k 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 Signed In Research?
Skills that share tags, products or a category with Signed In Research: Document Signing (asgeirtj/system_prompts_leaks, 69k stars), Dropbox Sign Automation (ComposioHQ/awesome-claude-skills, 77k stars), Implementing Code Signing For Artifacts (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Implementing Sigstore For Software Signing (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Signed In Research?
Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 115 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.
Source: Porabuild/Poracode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.