twenty-partner-recap

Pull recent Fireflies partner meetings, match each to an existing Partner record by attendee email or domain, write a recap (transcript-first, Fireflies summary as fallback), and inject it as a Note on the partner's profile. Use after a batch of partner calls when you want each partner's CRM record updated with what was said. Leads and discovery calls have no Partner match and are skipped. Pass --prune to delete the Fireflies recordings once the recaps are safely in the CRM.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable multi-phase workflow with strong validation and feedback loops for its batch and destructive operations. Minor conciseness trims and inlining of a couple of shared details would push it to the top anchor.

Suggestions

Trim justificational prose in the preamble (e.g. "Network upkeep, not the lead path" and the "5 of the 29" stat) to tighten token efficiency.

Inline a minimal gql() call example or the exact query shape for one mutation so the skill is executable without opening the shared file for the common case.

Confirm the referenced ../_shared/partner-api.md exists in the bundle (or relocate a one-line pointer into ./references/) so the progressive-disclosure reference is verifiable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and purposeful with no padding of concepts Claude already knows, though a few justificational asides ("Network upkeep, not the lead path", "Roughly 5 of the 29 validated partners have one today") could be trimmed.	4 / 5
Actionability	Provides concrete GraphQL field paths (persons.edges.node.emails.primaryEmail), named mutations (createNote, createNoteTarget, updateNote, deleteTranscript), a free-provider skip list, and a literal note template; gql/credentials are delegated to the shared file rather than inlined, leaving minor gaps.	4 / 5
Workflow Clarity	Six phases are clearly sequenced with explicit validation checkpoints and feedback loops: content-quality gating before writing (Phase 3), read-back verification of each note (Phase 4), and confirm-then-verify destruction in Phase 6—appropriate for a batch/destructive skill.	5 / 5
Progressive Disclosure	Well-organized into clearly headed phases with a single clearly-signaled one-level reference ("Credentials, the gql() helper and every query live in ../_shared/partner-api.md"); the referenced file is external to this skill's bundle and not independently verifiable, keeping it just below the top anchor.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that concretely states what the skill does and when to use it, with explicit edge-case and flag handling. Trigger phrasing is natural and the niche is highly distinct.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—"pull recent Fireflies partner meetings", "match each to an existing Partner record by attendee email or domain", "write a recap (transcript-first, Fireflies summary as fallback)", "inject it as a Note", and "Pass --prune to delete the Fireflies recordings"—giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both "what" (pull, match, recap, inject Note, prune) and "when" ("Use after a batch of partner calls when you want each partner's CRM record updated with what was said") with concrete trigger phrasing and edge-case handling (leads/discovery skipped).	5 / 5
Trigger Term Quality	Natural phrases users would say appear ("after a batch of partner calls", "recap", "CRM record updated with what was said"), but coverage of synonyms/variations is limited and no file-extension-style triggers apply to this niche.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche—Fireflies partner-meeting recaps injected as Notes on Twenty Partner profiles—with specific triggers unlikely to fire for any other skill.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: twentyhq/twenty
Path: packages/twenty-apps/internal/twenty-partners/src/skills/twenty-partner-recap/SKILL.md
Commit: 1749958

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.