{"version":"2.1.251","anchor":"document-and-report-skills-step-aside-for-a-first-party-conn","canonical_anchor":"document-and-report-skills-step-aside-for-a-first-party-conn","heading":"Document and report skills step aside for a first-party connector","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/document-and-report-skills-step-aside-for-a-first-party-conn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Document and report skills step aside for a first-party connector\n\nDocument and report skills stand aside when a first-party document connector is attached.\n\n**What**\n\nThe document and report artifact skills now describe themselves as deferring to an attached first-party document connector, so requests for pages, docs, memos, plans, notes and reports use that connector's tools instead of building an artifact.\n\n**Details**\n\n- Third-party tools such as Notion, Confluence or Google Docs integrations that are not host-designated never trigger this deferral.\n- The change is in the skill descriptions; whether it takes effect depends on a connector actually being attached.\n\n**Evidence**\n\n`Defers to a first-party connector (host-designated, never self-described) for reading and writing documents`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}