Automated summary
This skill walks through the initial development setup for internbot, a Slack bot, from creating the Slack app to running tests.
Strengths
- Precisely lists the OAuth scopes and Slack events to enable
- Covers creating the separate GitHub reports repository, including PAT-based authentication
- Ends with concrete test steps to validate the bot
Limitations
- Assumes the user already has a Slack workspace with app-creation rights
- Project-specific commands (npm install, npm run dev) are not detailed and depend on the existing repo
- Does not address troubleshooting for Socket Mode or missing-permission failures
Use when installing the internbot project for the first time on a new machine or for a new developer.
Do not use to modify the bot's behavior or add features once the environment is already set up.
Security analysis
CautionThe skill is a straightforward developer onboarding guide: Slack app creation, .env configuration, git init, npm install/run. Nothing is destructive, obfuscated, or exfiltrating — no curl|sh, no rm -rf, no sending data to third parties. The main concerns are security hygiene: plaintext PAT storage in .git/credentials and a PAT embedded in the remote URL, plus very broad Slack history scopes. These are practices worth flagging but they operate on the user's own credentials for their own repos, so 'caution' rather than 'risky'.
- •Step 3 instructs storing a GitHub PAT in plaintext at .git/credentials via `credential.helper store --file=.git/credentials`, and embedding the PAT directly in the git remote URL — a credential-exposure anti-pattern (the token persists in plaintext and in .git/config).
- •Requests a broad set of Slack scopes (channels:history, groups:history, im:history, mpim:history, etc.), giving the bot read access to essentially all workspace message history; legitimate for the stated purpose but worth flagging for least-privilege review.
- •The workflow assumes a bot running with repo write access and push rights to a separate GitHub repo; no guidance on token rotation, scoping the PAT, or keeping .env/.git credentials out of version control.
Examples
Je viens de cloner internbot, aide-moi à le configurer pour le développement sur ma machine.Quels scopes OAuth et quels events Slack dois-je activer pour que le bot internbot fonctionne ?Comment configurer le dépôt GitHub séparé où le bot publie ses rapports LaTeX ?name: onboard description: Set up internbot for development. Use when setting up the project for the first time.
Internbot Developer Setup
Prerequisites
- Node.js >= 20
- A Slack workspace where you can create apps
Steps
1. Create a Slack App
- Go to https://api.slack.com/apps → Create New App → From scratch
- Name it (e.g., "internbot"), select your workspace
- Enable Socket Mode under Settings → Socket Mode → toggle on
- Generate an app-level token with
connections:writescope → save asSLACK_APP_TOKEN
- Generate an app-level token with
- Under OAuth & Permissions, add these Bot Token Scopes:
app_mentions:readchannels:historychannels:readchat:writegroups:historygroups:readim:historyim:readim:writempim:historympim:readusers:readreactions:write
- Under Event Subscriptions → toggle on → Subscribe to bot events:
message.channelsmessage.groupsmessage.immessage.mpimapp_mention
- Install the app to your workspace → copy the Bot User OAuth Token as
SLACK_BOT_TOKEN
2. Configure Environment
cp .env.example .env
# Edit .env with your tokens:
# SLACK_BOT_TOKEN=xoxb-...
# SLACK_APP_TOKEN=xapp-...
3. Set Up Reports Repository
The bot publishes LaTeX reports to a separate GitHub repo. Set it up as a subdirectory:
mkdir reports-repo && cd reports-repo
git init
mkdir reports
echo '[]' > papers-log.json
git add . && git commit -m "init reports repo"
Create a GitHub repo for reports, then configure the remote with a dedicated account (optional):
git remote add origin https://<github-user>@github.com/<github-user>/<repo-name>.git
git config user.name "<bot-name>"
git config user.email "<github-user>@users.noreply.github.com"
git push -u origin main
If using a dedicated GitHub account, store its PAT locally:
echo "https://<github-user>:<PAT>@github.com" > .git/credentials
git config credential.helper 'store --file=.git/credentials'
4. Install & Run
npm install
npm run dev # Development with hot reload
npm run build # Compile TypeScript
npm start # Run compiled version
5. Test
- DM the bot "hi" → should get a simple reply
- In a channel, @mention the bot with a question → should get a threaded response
- Ask it to search for papers → should use arxiv tools
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/internbot-developer-setup-mrwak9io/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/internbot-developer-setup-mrwak9io' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/internbot-developer-setup-mrwak9io/download' --output '.skill-downloads/internbot-developer-setup-mrwak9io/SKILL.md.part' && mv '.skill-downloads/internbot-developer-setup-mrwak9io/SKILL.md.part' '.skill-downloads/internbot-developer-setup-mrwak9io/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Prerequisites
- Node.js >= 20
- A Slack workspace where you can create apps
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/internbot-developer-setup-mrwak9io/SKILL.md' && test -s '.skill-downloads/internbot-developer-setup-mrwak9io/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/onboard' && cp -R '.skill-downloads/internbot-developer-setup-mrwak9io' '.claude/skills/onboard'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/internbot-developer-setup-mrwak9io'openskills read 'internbot-developer-setup-mrwak9io'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/internbot-developer-setup-mrwak9io/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.