# Coordinate Metix People, Company, and Job Searches

Cross-dataset research requires linked records, valid filters, and careful credit planning. This skill guides Metix API workflows using live contracts, identifier chaining, and batched retrieval.

## Install

```bash
npx skillstore add metixai-official/metix-platform-assistant
```

## Metadata

- Status: approved
- Slug: metixai-official-metix-platform-assistant
- Skillstore revision: r1
- Version status: missing
- Tree hash: 482914a1bbf677111ce70366dbb6bfd93faa72f095bb8c7e55a8832913582cc0
- Author: metixai-official
- GitHub username: metixai-official
- Repository: https://github.com/metixai-official/metix-skills/tree/989f0b41515b405e4dd2ac73d527399f4f027746/skills/metix-platform-assistant
- Ref: 9938f91a9ab0f5763a54332b129295339bf829dd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 72
- Public page: https://skillstore.pages.dev/skills/metixai-official-metix-platform-assistant
- Manifest: https://skillstore.pages.dev/api/skills/metixai-official-metix-platform-assistant/manifest

## Capabilities

- Guide people, company, and job workflows using live API contract fields and supported query operators.
- Link job employers and profile experience to company details through company identifiers.
- Explain search-to-detail workflows and batch detail retrieval for up to 100 identifiers.
- Distinguish structured Query Spec searches from plain-language people search.
- Guide API error handling through error codes and linked Markdown documentation.
- Explain contact probing, paid unlocking, batch limits, authorization scope, and worst-case credit reservations.

## Use Cases

- Research employers before sourcing candidates: Connect relevant job postings to employer records, then retrieve people at those companies without requesting contact details.
- Enrich a focused prospect shortlist: Resolve company and people records, probe contact availability, and estimate worst-case charges before an authorized contact unlock.
- Plan efficient cross-dataset retrieval: Check contract compatibility and credit balance, select valid filters, and batch detail requests for a large research run.

## Prompt Templates

### Understand the available datasets

```
Explain how Metix people, company, and job data connect. Outline the required access and free checks. Do not run paid requests.
```

### Resolve a job employer

```
For Metix job identifier [job_id], check the live contract, retrieve its title and company identifier, then retrieve that company. Exclude contact retrieval.
```

### Build a cross-dataset research plan

```
Plan a search for senior engineers at companies hiring for [role] in [location]. Use live contract fields and narrow before profile details. Estimate credits before paid calls.
```

### Design a controlled enrichment run

```
Design a Metix enrichment run for [shortlist] within [credit_budget]. Check key status, contract limits, batching, and contact availability. Quote worst-case unlock reservations. Wait for approval before unlocking.
```

## Limitations

- Provides instructions and examples, not a bundled executable client or dataset.
- Authenticated operations require METIX\_KEY and network access; paid contact unlocking has additional account and permission requirements.
- Current field names, limits, and prices depend on the live contract and documentation.
- The API retrieves records but does not provide a person-to-role scoring or ranking endpoint.

## Best Practices

- Read the live contract before building filters, and link datasets using returned identifiers rather than names.
- Narrow searches before detail retrieval, batch identifiers, and check remaining credits before large runs.
- Keep METIX\_KEY out of output and files; confirm contact access authorization and worst-case charges before unlocking.

## Anti Patterns

- Guessing field names, using unsupported operators, or sending structured filters to plain-language people search.
- Retrieving one identifier per request or unlocking contacts before narrowing the shortlist and checking costs.
- Searching the machine for substitute credentials or requesting a nonexistent person-to-role scoring endpoint.

## Security Audit

- Audited at: 2026-11-09T03:09:33.346\+00:00
- Summary: All 45 static findings are false positives involving Markdown formatting, documented Metix URLs, or ordinary API examples. No evidence found of prompt injection, system reconnaissance, or unauthorized exfiltration in SKILL.md. The skill requires external API access and credentials, with explicit key protection rules and paid contact retrieval limits.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0