Filescope MCP
admica/FileScopeMCP
Codebase intelligence via FileScopeMCP — symbol lookup, dependency mapping, importance ranking, and semantic search.
Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform.
$ npx skills add caliber-ai-org/ai-setup --skill writers-pattern -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install caliber-ai-org/ai-setup writers-pattern --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/caliber-ai-org/ai-setup.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writers-pattern .claude/skills/writers-pattern && 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 "writers-pattern" agent skill from https://github.com/caliber-ai-org/ai-setup/tree/master/skills/writers-pattern into .claude/skills/writers-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writers-pattern", 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/caliber-ai-org/ai-setup/tree/master/skills/writers-patternType 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 caliber-ai-org/ai-setup --skill writers-pattern -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install caliber-ai-org/ai-setup writers-pattern --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caliber-ai-org/ai-setup.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writers-pattern .agents/skills/writers-pattern && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writers-pattern" agent skill from https://github.com/caliber-ai-org/ai-setup/tree/master/skills/writers-pattern into .agents/skills/writers-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writers-pattern", 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 caliber-ai-org/ai-setup --skill writers-pattern -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install caliber-ai-org/ai-setup writers-pattern --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caliber-ai-org/ai-setup.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writers-pattern .cursor/skills/writers-pattern && 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 "writers-pattern" agent skill from https://github.com/caliber-ai-org/ai-setup/tree/master/skills/writers-pattern into .cursor/skills/writers-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writers-pattern", 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/caliber-ai-org/ai-setup.git --path skills/writers-pattern--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 caliber-ai-org/ai-setup --skill writers-pattern -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install caliber-ai-org/ai-setup writers-pattern --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caliber-ai-org/ai-setup.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writers-pattern .gemini/skills/writers-pattern && 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 "writers-pattern" agent skill from https://github.com/caliber-ai-org/ai-setup/tree/master/skills/writers-pattern into .gemini/skills/writers-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writers-pattern", 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 caliber-ai-org/ai-setup writers-patternInstalls 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 caliber-ai-org/ai-setup --skill writers-pattern -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/caliber-ai-org/ai-setup.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writers-pattern .github/skills/writers-pattern && 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 "writers-pattern" agent skill from https://github.com/caliber-ai-org/ai-setup/tree/master/skills/writers-pattern into .github/skills/writers-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writers-pattern", 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 caliber-ai-org/ai-setup --skill writers-pattern -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install caliber-ai-org/ai-setup writers-pattern --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caliber-ai-org/ai-setup.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writers-pattern .opencode/skills/writers-pattern && 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 "writers-pattern" agent skill from https://github.com/caliber-ai-org/ai-setup/tree/master/skills/writers-pattern into .opencode/skills/writers-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writers-pattern", 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.
writers-patternAdd a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform.
Writers Pattern is an agent skill from caliber-ai-org/ai-setup. Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform. Each writer exports a function that accepts a config interface, creates directories (rules/, skills/, mcp configs), writes files with proper formatting and frontmatter, and returns string[] of written file paths. Use when adding platform support for a new agent, integrating a new code AI tool, or extending caliber to support new targets. Do NOT use for modifying existing writers, refactoring…
Its SKILL.md is about 3.7k 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 Development, covering Refactoring. It works with Model Context Protocol. The repository describes itself as: Continuously sync your AI setups with one command. Codebase tailor suited agent skills, MCPs and config files for Claude Code, Cursor, and Codex. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit f5dbc00. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Writers Pattern loads about 3.7k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 1,253 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.
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.
The full file from caliber-ai-org/ai-setup at commit f5dbc00, republished under its MIT licence (© caliber-ai-org). 1,253 words, ~3,727 tokens.
.claude/skills/writers-pattern/SKILL.md (or your agent's skills folder).Every writer MUST:
write<Platform>Config(config: <PlatformConfig>): string[]string[] of all written file paths (used by manifest and progress display)fs.mkdirSync(dir, { recursive: true }) before writing files--- markers).claude/, CLAUDE.md, .mcp.json)Integration point: Every writer MUST be imported and called in src/writers/index.ts within the writeSetup() function. Missing this step means the writer will never execute.
Validation before Step 1: Verify the platform name is unique (ls src/writers/ shows no <platform>/index.ts). If it exists, you are modifying, not adding.
Verify the platform name is unique (see Critical). Create src/writers/<platform>/index.ts.
At the top of the file, define a config interface that describes all content the writer accepts. The interface MUST include:
claudeMd, cursorrules, agentsMd, instructions)rules, skills, mcpServers, instructionFiles, etc.name or filename, content, and for skills, descriptionExample (matching GitHub Copilot pattern already in codebase):
interface CopilotConfig {
instructions: string; // Main content
instructionFiles?: Array<{ filename: string; content: string }>;
}Validation: Confirm the interface property names match platform conventions (e.g., Claude uses claudeMd, Cursor uses cursorrules). Check existing writers: src/writers/claude/index.ts line 9, src/writers/cursor/index.ts line 9, src/writers/codex/index.ts line 5.
Export a function named write<Platform>Config(config: <PlatformConfig>): string[] that:
Initialize an empty written: string[] = [] array to track all written paths.
For the main config file (e.g., CLAUDE.md for Claude, .cursorrules for Cursor):
src/writers/pre-commit-block.tsappendPreCommitBlock(content, platform), appendLearningsBlock(content), appendSyncBlock(content)src/writers/claude/index.ts line 19-22): appendSyncBlock(appendLearningsBlock(appendPreCommitBlock(config.claudeMd)))src/writers/cursor/index.ts line 19-22): No sync block; injects rules instead (pre-commit, learnings, sync as separate files)src/writers/codex/index.ts line 13-16): appendLearningsBlock(appendPreCommitBlock(config.agentsMd, 'codex'))src/writers/github-copilot/index.ts line 19-22): appendSyncBlock(appendLearningsBlock(appendPreCommitBlock(config.instructions, 'copilot')))fs.writeFileSync('CLAUDE.md', wrappedContent)) and push to written.For rules (if applicable): Platform convention determines directory.
.cursor/rules/, Claude uses .claude/rules/ (see src/writers/index.ts lines 123-126 and 135-137)<dir>/<rule.filename>, push path to writtensrc/writers/cursor/index.ts line 24-27): Cursor injects three system rules:const preCommitRule = getCursorPreCommitRule();
const learningsRule = getCursorLearningsRule();
const syncRule = getCursorSyncRule();
const allRules = [...(config.rules || []), preCommitRule, learningsRule, syncRule];For skills: Write with YAML frontmatter.
.claude/skills/<skillName>/SKILL.md, .cursor/skills/<skillName>/SKILL.md, .agents/skills/<skillName>/SKILL.md, .opencode/skills/<skillName>/SKILL.mdsrc/writers/claude/index.ts line 40-47):---
name: <skill.name>
description: <skill.description>
paths:
- <optional path pattern 1>
- <optional path pattern 2>
---
<skill.content>src/writers/opencode/index.ts line 30): Use buildSkillContent(skill) from src/lib/builtin-skills.js instead of manual frontmatter.fs.mkdirSync(skillDir, { recursive: true }), write skill, push to writtenFor MCP Servers (if applicable): Write/merge JSON at platform-specific path.
src/writers/claude/index.ts line 54-65): .mcp.json at rootsrc/writers/cursor/index.ts line 54-69): .cursor/mcp.json{ ...existingServers, ...config.mcpServers }, write merged object{ mcpServers: mergedServers } and output as pretty-printed JSON: JSON.stringify(wrapped, null, 2)For instruction files (GitHub Copilot, src/writers/github-copilot/index.ts line 26-33): Write to .github/instructions/ directory.
<dir>/<file.filename>, push pathsReturn the written array.
Validation: Confirm all file write operations are synchronous (fs.writeFileSync, fs.mkdirSync). Ensure every written path is added to the array. No async operations allowed.
If the config interface may be reused elsewhere (e.g., in src/writers/index.ts for the AgentSetup type), export the interface from the module.
Validation: Check src/writers/index.ts lines 15-19 to see if new agent setup params are needed.
src/writers/index.tsOpen src/writers/index.ts. At the top (around line 2-6), add:
import { write<Platform>Config } from './<platform>/index.js';Update the AgentSetup interface (around line 12-20):
'<platform>' to the targetAgent tuple (line 13: ('claude' | 'cursor' | 'codex' | 'opencode' | 'github-copilot' | '<platform>')[])<platform>?: Parameters<typeof write<Platform>Config>[0];Update getFilesToWrite() function (starting line 117): Add a new conditional block:
if (setup.targetAgent.includes('<platform>') && setup.<platform>) {
files.push('<main-config-file>');
if (setup.<platform>.rules) {
for (const r of setup.<platform>.rules) files.push(`<rules-dir>/${r.filename}`);
}
if (setup.<platform>.skills) {
for (const s of setup.<platform>.skills) files.push(`<skills-dir>/${s.name}/SKILL.md`);
}
// ... repeat for other config types (mcpServers, instructionFiles, etc.)
}Update writeSetup() function (starting line 22): Add a new conditional block before the return (after line 56):
if (setup.targetAgent.includes('<platform>') && setup.<platform>) {
written.push(...write<Platform>Config(setup.<platform>));
}Validation: Confirm the function call order in writeSetup() is consistent (line 37-56): claude → cursor → codex → opencode → github-copilot → (new platform). This ensures AGENTS.md is written once if shared (as with Codex/Opencode, see line 50-52).
Create src/writers/__tests__/<platform>.test.ts following the vitest pattern in src/writers/__tests__/codex.test.ts:
fs module: vi.mock('fs')beforeEach: vi.mocked(fs.existsSync).mockReturnValue(false).toHaveBeenCalledWith(path, { recursive: true }))vi.mocked(fs.writeFileSync).mock.calls).toContain('caliber:managed:pre-commit'))Run: npm test -- src/writers/__tests__/<platform>.test.ts
Validation: All tests pass. Confirm mocked file operations match actual file system structure.
detectSyncedAgents() in src/commands/refresh.ts (Optional)If the platform writes config files with distinct naming (e.g., .newplatform/), update the detection logic around line 68-77 so end-user refresh output correctly identifies the synced platform:
if (joined.includes('.newplatform/') || joined.includes('newplatform-config')) {
agents.push('<Platform Name>');
}Validation: Run npm run refresh and confirm the summary message lists the new platform.
User says: "Add support for DevCode, a new agent that reads config from .devcode/settings.md and .devcode/rules/ directory."
Actions taken:
Create src/writers/devcode/index.ts (matching pattern from src/writers/claude/index.ts):
import fs from 'fs';
import path from 'path';
import { appendPreCommitBlock, appendLearningsBlock } from '../pre-commit-block.js';
interface DevcodeConfig {
settingsMd: string;
rules?: Array<{ filename: string; content: string }>;
}
export function writeDevcodeConfig(config: DevcodeConfig): string[] {
const written: string[] = [];
fs.writeFileSync(
'.devcode/settings.md',
appendLearningsBlock(appendPreCommitBlock(config.settingsMd, 'devcode'))
);
written.push('.devcode/settings.md');
if (config.rules?.length) {
const rulesDir = path.join('.devcode', 'rules');
if (!fs.existsSync(rulesDir)) fs.mkdirSync(rulesDir, { recursive: true });
for (const rule of config.rules) {
const rulePath = path.join(rulesDir, rule.filename);
fs.writeFileSync(rulePath, rule.content);
written.push(rulePath);
}
}
return written;
}Update src/writers/index.ts:
import { writeDevcodeConfig } from './devcode/index.js';targetAgent tuple to include 'devcode'devcode?: Parameters<typeof writeDevcodeConfig>[0];getFilesToWrite() (match Codex pattern lines 144-149)writeSetup() (match Codex pattern lines 45-47)detectSyncedAgents() to check for .devcode/Create src/writers/__tests__/devcode.test.ts (matching src/writers/__tests__/codex.test.ts):
import { describe, it, expect, vi, beforeEach } from 'vitest';
import fs from 'fs';
import path from 'path';
vi.mock('fs');
import { writeDevcodeConfig } from '../devcode/index.js';
describe('writeDevcodeConfig', () => {
beforeEach(() => {
vi.clearAllMocks();
vi.mocked(fs.existsSync).mockReturnValue(false);
});
it('writes settings.md and rules', () => {
const config = {
settingsMd: '# DevCode Config',
rules: [{ filename: 'style.md', content: 'Style rules' }],
};
const written = writeDevcodeConfig(config);
expect(written).toContain('.devcode/settings.md');
expect(written).toContain(path.join('.devcode', 'rules', 'style.md'));
});
});Run: npm test && npm run build
Result: Caliber now generates .devcode/settings.md and rules on caliber refresh and caliber init.
Issue: "TypeError: write<Platform>Config is not a function"
export function write<Platform>Config(...) in the writer file. Missing export is a common mistake.Issue: "ENOENT: no such file or directory, open '.platform/config.md'"
fs.mkdirSync(parentDir, { recursive: true }) is called before fs.writeFileSync(filePath, content). See correct order in src/writers/claude/index.ts lines 26-27.Issue: "Skill file has no frontmatter / malformed YAML"
---\nname: <name>\ndescription: <desc>\n---\n<content>[...].join('\n') and test with a single skill first. Compare with working code in src/writers/claude/index.ts lines 40-48.Issue: "MCP servers not merging, file is truncated"
src/writers/claude/index.ts line 54-65: read existing JSON (with try/catch), parse safely, merge with spread operator { ...existingServers, ...config.mcpServers }, then write the merged object. Do NOT overwrite — always merge.Issue: "new writer is called but written files are empty array"
written array. Check that every file operation pushes to written. Missing a written.push(filePath) after fs.writeFileSync() is the most common error. See src/writers/codex/index.ts lines 17 and 32 for correct pattern.Issue: "Tests mock fs but actual files are created in .tmp/ or cause permission errors"
vi.mock('fs') is at the top of the test file before any imports. All fs operations will be mocked and return mock values from beforeEach setup. See src/writers/__tests__/codex.test.ts line 5.Issue: "Cursor pre-commit rule not applied, or learnings block missing"
getCursorPreCommitRule(), getCursorLearningsRule(), and getCursorSyncRule() are called and concatenated with user rules before iterating (see src/writers/cursor/index.ts lines 24-27). Claude and Codex use block-append helpers instead.© caliber-ai-org, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/writers-pattern of caliber-ai-org/ai-setup.
Open the folder on GitHubat commit f5dbc00
Writers Pattern 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 |
|---|---|---|---|---|---|---|
| Writers Pattern this skillcaliber-ai-org/ai-setup | 1.3k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Filescope MCPadmica/FileScopeMCP | 302 | — | ~1.7k | Automated safety check: Pass | Proprietary | |
| Gograph Go Repository Intelligenceozgurcd/gograph | 228 | — | ~4.8k | Automated safety check: Notes | MIT | |
| Memtrace Decision Memorysyncable-dev/memtrace-public | 489 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Testing With API Mocksstacklok/toolhive-studio | 170 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Edt MCP Project Local FixDitriXNew/EDT-MCP | 295 | — | ~507 | Automated safety check: Pass | AGPL-3.0 |
admica/FileScopeMCP
Codebase intelligence via FileScopeMCP — symbol lookup, dependency mapping, importance ranking, and semantic search.
ozgurcd/gograph
Gives an agent working in a Go codebase a structural view through a local MCP server: call graphs, blast-radius and impact analysis, and bounded first-call exploration.
syncable-dev/memtrace-public
Use Cortex decision memory through the normal Memtrace MCP tools.
stacklok/toolhive-studio
Start here for all API mocking in tests. An agent skill from stacklok/toolhive-studio.
DitriXNew/EDT-MCP
Apply one bounded BSL correction through EDT-MCP with lost-update protection, targeted validation, and minimal diff.
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
caliber-ai-org/ai-setup
Creates a new CLI command following the Commander.js pattern in src/commands/.
caliber-ai-org/ai-setup
Writes Vitest tests following project patterns: tests/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment…
caliber-ai-org/ai-setup
Discovers and installs community skills from the public registry.
caliber-ai-org/ai-setup
Adds a new LLM provider implementing LLMProvider interface with call() and stream() methods.
caliber-ai-org/ai-setup
Saves user instructions as persistent learnings for future sessions.
caliber-ai-org/ai-setup
Add a new deterministic scoring check in src/scoring/checks/ that evaluates config quality.
Works with
Categories
Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform. Writers Pattern is an agent skill from caliber-ai-org/ai-setup. Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform.
Writers Pattern fits situations like: adding platform support for a new agent; integrating a new code AI tool; extending caliber to support new targets; modifying existing writers.
Run `npx skills add caliber-ai-org/ai-setup --skill writers-pattern -a claude-code`. Or copy the skill folder (skills/writers-pattern in caliber-ai-org/ai-setup) into .claude/skills/writers-pattern in your project. Claude Code loads it when a task matches its description.
Run `npx skills add caliber-ai-org/ai-setup --skill writers-pattern -a codex`. Or copy the skill folder (skills/writers-pattern in caliber-ai-org/ai-setup) into .agents/skills/writers-pattern in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add caliber-ai-org/ai-setup --skill writers-pattern -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writers-pattern, .gemini/skills/writers-pattern, .github/skills/writers-pattern and .opencode/skills/writers-pattern in your project.
Going by SKILL.md and its folder, Writers Pattern needs the command-line tools its instructions call (npm).
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Writers Pattern is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Writers Pattern: Filescope MCP (admica/FileScopeMCP, 302 stars), Gograph Go Repository Intelligence (ozgurcd/gograph, 228 stars), Memtrace Decision Memory (syncable-dev/memtrace-public, 489 stars) and Testing With API Mocks (stacklok/toolhive-studio, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
caliber-ai-org (a GitHub organization) maintains it in caliber-ai-org/ai-setup, which has 1,301 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 24, 2026.
Source: caliber-ai-org/ai-setup on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.