ai-assistant-editor-setup
Skill0 starsChanged 19 days agoMITView on GitHub
Use when setting up an AI assistant extension in VS Code.
In this repository86 other files it gives its agents.
- api-and-interface-designSkill
- banner-designSkill
- brainstormingSkill
- caveman-exploreSkill
- caveman-reviewSkill
- chat-silence-diagnosisSkill
- ci-cd-and-automationSkill
- code-auditSkill
- codebase-designSkill
- koordinator-team-dispatchSkill
- constraint-driven-developmentSkill
- context-engineeringSkill
- cpanel-shared-hosting-deploySkill
- cross-profile-cron-opsSkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- domain-modelingSkill
- doubt-driven-developmentSkill
- finishing-a-development-branchSkill
- frontend-designSkill
- git-workflow-and-versioningSkill
- graphic-design-laneSkill
- hermes-gateway-web-uiSkill
- hermes-profile-hygieneSkill
- hermes-profile-provisioningSkill
- hermes-service-persistenceSkill
- hermes-stream-stale-diagnosisSkill
- hermes-team-dashboardSkill
- idea-refineSkill
- incremental-implementationSkill
- indonesian-official-lettersSkill
- internal-commsSkill
- interview-meSkill
- investigate-firstSkill
- kanban-rate-limit-resilienceSkill
- karpathy-guidelinesSkill
- large-project-gated-deliverySkill
- lean-buildSkill
- live-agent-office-operationsSkill
- live-react-runtime-qaSkill
- live-web-release-verificationSkill
- markdown-pdf-pipelineSkill
- marketing-strategySkill
- meta-social-publishingSkill
- meta-threads-oauth-lifecycleSkill
- migrationSkill
- multi-profile-project-orchestrationSkill
- network-operationsSkill
- observability-and-instrumentationSkill
- office-skill-distributionSkill
- organization-site-menu-researchSkill
- performance-optimizationSkill
- php-upload-size-limitsSkill
- planning-and-task-breakdownSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-reviewSkill
- ponytailSkill
- portable-app-handoffSkill
- receiving-code-reviewSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Verify → send a trivial test message and confirm it can read a workspace file before declaring the setup done.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI assistant setup in a desktop editor
When to Use
User asks to install, enable, or configure an AI coding assistant inside VS Code or a derivative (Cursor, Windsurf, VSCodium) — first-time provider setup (e.g. Cline), or "it doesn't open / doesn't respond".
Procedure
- Open the assistant from ITS OWN activity-bar icon (or its command in the Command Palette). Never start from the editor's built-in Chat panel — that is a different assistant and will answer setup instructions confidently while the target one stays unconfigured.
- Gear icon in the assistant's panel → API Provider. Choose managed account/subscription, or BYOK when the user already has a proxy or API key (usually cheapest for a user who pays for a proxy).
- BYOK endpoint styles:
- Anthropic-style proxy: provider
Anthropic, Base URL = the proxy endpoint, paste key. - OpenAI-style: provider
OpenAI Compatible, Base URL ends in/v1with NO trailing slash, paste key, type the exact Model ID (custom endpoints do not auto-populate model lists).
- Anthropic-style proxy: provider
- Fill the collapsible Model Configuration: context window, max output tokens, price (display only), and tool/computer-use mode ON — with it off the assistant is chat-only and file/terminal actions silently no-op.
- Verify → send a trivial test message and confirm it can read a workspace file before declaring the setup done.
Pitfalls
- Two variants of the same assistant installed (stable + nightly/preview) split its commands: palette entries return "No matching results". Keep one variant (prefer the stable marketplace build), uninstall the other, fully restart the editor (File → Exit, not reload window).
- The activity bar can be moved or hidden — the tell is explorer icons
on the RIGHT edge of the window. There is no "Show Activity Bar" command
(searching it returns "No matching results" and looks like the feature is
gone); use
View: Move Activity Bar to Side, then right-click the bar and re-enable the assistant's icon. - UI field names move between versions — check the vendor docs (Cline: docs.cline.bot) for current labels instead of asserting them from memory.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

