fix(skills): prioritize Alexandria tools and include the skill in catalogue sync

[ericciarla]

Summary

Research requests can select ordinary web search even when Alexandria is installed. Make the skills follow this workflow:

1. Understand the user's intent, constraints, and required results.
2. Discover relevant tools with a natural-language query or inferred/known provider filters, even when the user names no providers.
3. Obtain the full definitions of selected tools before executing them.
4. Call tools, inspect results, paginate, refine inputs, fetch details, and use complementary providers until the requested information is collected.
5. Fall back to ordinary web research for remaining gaps only when relevant provider capabilities are exhausted or unavailable.

The Alexandria skill distinguishes semantic tool search from find-tools catalogue filters, explains full-definition expansion and pagination, and corrects invalid_option discovery errors. It checks that capabilities support the requested operation, such as rentals versus for-sale listings. The general Firecrawl and Search skills use the same workflow when Alexandria is installed.

Skill location and distribution

Move Alexandria from beta-skills/firecrawl-alexandria/ to skills/firecrawl-alexandria/ and use Alexandria as its product name. Update the npm package file list, firecrawl setup alexandria source path, and its setup test so the bundled installation keeps working.

The existing skills/** catalogue-sync workflow will now copy Alexandria into firecrawl/skills under skills/core/firecrawl-alexandria/ after merge. The skill remains authored in this repository; no manual edits to the catalogue mirror are needed. Existing core-install selection lists and the @alexandria npm tag remain unchanged.

Provider integrations are unchanged; existing execution budget, access, and retry rules remain in place.

Validation

• pnpm run format:check passed.
• pnpm run build passed.
• All 442 tests passed across the full run and the targeted rerun: 434 passed initially; the eight Alexandria integration tests needed a rerun outside the sandbox to allow their localhost mock server.
• npm pack --dry-run --ignore-scripts verified that the package includes skills/firecrawl-alexandria/SKILL.md and contains no beta-skills/ paths.
• Skill frontmatter validation and git diff --check passed.
• Reviewed command and response guidance against the installed CLI and live catalogue responses. Future-agent behavioral evaluation was not run.

Follow-up (outside this PR)

• After the testing period, align Alexandria installation with the other core skills: add firecrawl-alexandria to the default CLI_SKILLS selection and route its setup through the standard central-catalogue installer. Keep explicit installation during testing.

[cubic-dev-ai]

1 issue found across 3 files

Confidence score: 3/5

• skills/firecrawl-search/SKILL.md: the Alexandria discovery command is excluded by the current allowed-tools pattern, so the skill may block or fail to authorize the new npx firecrawl-cli@alexandria ... invocation; update the rule to explicitly cover the Alexandria command form.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="skills/firecrawl-search/SKILL.md">

<violation number="1" location="skills/firecrawl-search/SKILL.md:16">
P2: The new Alexandria discovery command is not covered by this skill's `allowed-tools` rule: `Bash(npx firecrawl-cli *)` does not match `npx firecrawl-cli@alexandria ...` because the wildcard requires a word boundary after `firecrawl-cli`. Add an explicit `Bash(npx firecrawl-cli@alexandria *)` rule to both regular skill frontmatters, or invoke Alexandria through an already-allowed command.</violation>
</file>

<sub>Shadow auto-approve: would not auto-approve because issues were found.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The new Alexandria discovery command is not covered by this skill's allowed-tools rule: Bash(npx firecrawl-cli *) does not match npx firecrawl-cli@alexandria ... because the wildcard requires a word boundary after firecrawl-cli. Add an explicit Bash(npx firecrawl-cli@alexandria *) rule to both regular skill frontmatters, or invoke Alexandria through an already-allowed command.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At skills/firecrawl-search/SKILL.md, line 16:

<comment>The new Alexandria discovery command is not covered by this skill's `allowed-tools` rule: `Bash(npx firecrawl-cli *)` does not match `npx firecrawl-cli@alexandria ...` because the wildcard requires a word boundary after `firecrawl-cli`. Add an explicit `Bash(npx firecrawl-cli@alexandria *)` rule to both regular skill frontmatters, or invoke Alexandria through an already-allowed command.</comment>

<file context>
@@ -11,6 +11,10 @@ allowed-tools:
 
+## Provider discovery before web search
+
+When the Alexandria beta skill is installed and available, load `firecrawl-alexandria` first for research, comparisons, and data gathering, even when the user names no provider. Discover relevant tools with `npx firecrawl-cli@alexandria search "<required information and operation>" --sources alexandria --json`, then inspect relevant provider catalogues with `find-tools`. Use multiple complementary providers when useful and within the authorized budget. Use ordinary web search when provider tools cannot cover the request or its remaining information gaps after focused discovery. Honor explicit source/method restrictions; direct page extraction and local-file work do not require this discovery step. When Alexandria is unavailable, use the applicable workflow below.
+
 ## Quick start
</file context>

[cubic-dev-ai]

0 issues found across 3 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would not auto-approve. Auto-approval blocked by 1 unresolved issue from previous reviews.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 4 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would not auto-approve. Auto-approval blocked by 1 unresolved issue from previous reviews.

Re-trigger cubic</sub>