upstash/context7 · info
No dependencies detected
Error message
No dependencies detected
What it means
Emitted by `ctx7 skills suggest` at step 1 when detectProjectDependencies(process.cwd()) returned an empty array — the scanner found no supported dependency manifest in the current working directory, so there is nothing to match skills against. The CLI hints at manual search (`ctx7 skills search <keyword>`) and returns before any backend call or auth is attempted.
Source
Thrown at packages/cli/src/commands/skill.ts:836
}
log.plain(
`${pc.bold("Quick commands:")}\n` +
` Install all: ${pc.cyan(`ctx7 skills install ${repo} --all`)}\n` +
` Install one: ${pc.cyan(`ctx7 skills install ${repo} ${data.skills[0]?.name}`)}\n`
);
}
async function suggestCommand(options: SuggestOptions): Promise<void> {
trackEvent("command", { name: "suggest" });
log.blank();
// Step 1: Detect dependencies
const scanSpinner = ora("Scanning project dependencies...").start();
const deps = await detectProjectDependencies(process.cwd());
if (deps.length === 0) {
scanSpinner.warn(pc.yellow("No dependencies detected"));
log.info(`Try ${pc.cyan("ctx7 skills search <keyword>")} to search manually`);
return;
}
scanSpinner.succeed(`Found ${deps.length} dependencies`);
// Step 2: Single API call to backend
const searchSpinner = ora("Finding matching skills...").start();
const accessToken = await getValidAccessToken();
let data;
try {
data = await suggestSkills(deps, accessToken);
} catch {
searchSpinner.fail(pc.red("Failed to connect to Context7"));
return;
}View on GitHub (pinned to 5284672feb)
Solutions
- cd to the project root that actually contains package.json (or the equivalent manifest) and re-run
- If you already know the stack, use manual search: `ctx7 skills search <keyword>`
- Add/commit a dependency manifest for your stack, then retry suggest
- Verify with `ls` that a manifest file exists in the exact directory you are invoking from
Example fix
# before $ cd packages/web && ctx7 skills suggest No dependencies detected # after $ cd /path/to/repo-root && ctx7 skills suggest
Defensive patterns
Strategy: validation
Validate before calling
// Confirm a supported manifest exists in cwd before running suggest
import { access } from "node:fs/promises";
import { join } from "node:path";
const MANIFESTS = ["package.json", "pyproject.toml", "go.mod", "Cargo.toml", "composer.json"];
async function hasManifest(cwd: string): Promise<boolean> {
for (const m of MANIFESTS) {
try {
await access(join(cwd, m));
return true;
} catch {}
}
return false;
}
if (!(await hasManifest(process.cwd()))) {
console.error("Run from the project root containing a dependency manifest");
} Prevention
- Invoke ctx7 from the repo root, not a nested package folder
- Keep at least one standard manifest in the project root
- When no manifest is possible, script `ctx7 skills search <keyword>` instead of suggest
When it happens
Trigger: Run `ctx7 skills suggest` in an empty directory, home dir, or a folder without package.json/pyproject.toml/go.mod etc.; run it from a subdirectory (e.g. packages/web) while the manifest sits at the repo root; project uses a manifest format the detector does not support.
Common situations: Running the CLI from the wrong cwd (nested folder, git bare repo); scaffolding a brand-new project before adding dependencies; polyglot repos where the detector only recognizes specific manifests; shell configured to start in ~.
Related errors
- No matching skills found for your dependencies
- This skill contains potentially malicious content and cannot
- No skills found in ${repo}
- Review other skills from this repository carefully before in
- Installation cancelled
AI-assisted analysis of upstash/context7@5284672feb (2026-08-18).
Data as JSON: /api/errors/b7253165b4227ef9.
Report an issue: GitHub.