Skip to content

AIFACTORY-FEAT-184: AI skills library template: skill packages the registry publishes and the agent host loads

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.

A design artefact, not a tracker

This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).

Epic Ecosystem component extensions · Increment I1 Generate a microservice · State elaborated · Route backend-developer · Phase before development · Build order 27 of 185 (Templates and libraries)

Before development

Template or library work: every task of this feature changes a template or a shared library the Factory builds on, and it lands before the Factory's own repositories of I1 are developed. The mark travels with every task (tag phase:before-development).

A skill the Factory publishes as an asset (AssetKind Skill in AgentRegistryService, SkillManifest in asset-manifests.schema.json) may be implemented as a compiled package of AIFunctions; the AI skills library template (connectsoft-aiskills-library) scaffolds such a package on the Microsoft Agent Framework with an orchestrator function and supporting functions, immutable request and result records, typed error codes, redaction through Microsoft.Extensions.Compliance and ConnectSoft.Extensions.Compliance, an embeddings pipeline on Microsoft.Extensions.VectorData, an MCP tool wrapper and a Microsoft Learn MCP client, with contract, serialization, DI and telemetry tests. Its pages are out of step with its code: the Features page is the library template''s copied (UseDI and UseTracing where the symbols are useDI and no tracing switch exists), the versioning page names Semantic Kernel and .NET 8 and 9 while the code is on the Agent Framework (ADR-0002) and net10, and a Framework choice and a targetFrameworks string coexist. For the Factory the package must carry its SkillManifest, expose its functions as governed tools under the caller''s scope, redact and measure on the Factory conventions, and build across its parameters before the package publishes. Generating skill packages from skill definitions belongs to the Factory assets epic once the chain runs. Component: AI skills library template (extend).

Delivers —
Stubs —
Realizes components: cmp-aiskills-library-template
adrs: ADR-0002, ADR-0013, ADR-0019, ADR-0021, ADR-0022
Requirements —
Depends on AIFACTORY-FEAT-183 Library template: target frameworks, a manifest and Factory diagnostics for generated libraries
AIFACTORY-FEAT-090 Contracts package from the published schemas
AIFACTORY-FEAT-098 Model Context Protocol library: authenticated by default
AIFACTORY-FEAT-175 Observability libraries: the Factory telemetry conventions as one registration
AIFACTORY-FEAT-177 Compliance library: the Factory data classes and redaction profiles
Sources model/components.yaml, model/templates.yaml, model/services/control-plane/AgentRegistryService.yaml, docs/reference/schemas/asset-manifests.schema.json, ConnectSoft.AISkillsLibraryTemplate/README.md, ConnectSoft.AISkillsLibraryTemplate/docs/Features.md, ConnectSoft.AISkillsLibraryTemplate/TEMPLATE_VERSIONING.md, ConnectSoft.AISkillsLibraryTemplate/.template.config/template.json

AIFACTORY-US-309: AI skills library template: under UseFactoryProfile the generated package carries a SkillManifest that validates against the schema and names every function of the package

enabling · persona asset-maintainer As an asset maintainer, I want a skill package generated from the template to carry the manifest the registry needs, so that the package can be submitted as a Skill release candidate without a manifest written by hand.

AgentRegistryService publishes a skill as an asset of kind Skill, and the SkillManifest of docs/reference/schemas/asset-manifests.schema.json is its document: id, version, name, purpose, inputs and outputs are required, and requires, compatibility, tests, evaluations and failure modes are optional. The AI skills library template scaffolds a package of AIFunctions on the Microsoft Agent Framework with an orchestrator function and supporting functions, immutable request and result records and typed error codes, but nothing in the generated package describes it as a skill. This PBI adds the manifest as part of the Factory shape of the template. The amendment of ADR-0028 on the Factory profile switch puts the Factory shape of every template behind the boolean parameter UseFactoryProfile, off by default, so that other generations do not change; this PBI defines that parameter for the template, and the later PBIs of this file put their work under it. The template also gains parameters for the skill id and the purpose, which take effect only under the profile; the name comes from the library name. Under the profile the generated package holds a manifest file beside the code that is packed into the package. Its inputs and outputs name the request and result records of the functions with their descriptors, compatibility.libraries lists the packages the library pins, tests lists the test projects and evaluations names the suites the release gate runs. The manifest holds no evaluation result: the evaluation record of ADR-0021 is attached by the gate when the candidate is evaluated, not by the package. A test of the generated solution validates the manifest against the schema, which the solution takes from the contracts package by a version pin made only under the profile, and a second test fails when a function of the package is missing from the manifest or the manifest names a function that does not exist. The manifest is what a maintainer submits to AgentRegistryService as the release candidate, with the hash of the package in the dependency closure. A package generated without the profile equals the output of the current template: it holds no manifest, restores no Factory package and ignores the two parameters.

Acceptance criteria

AC1 Given a skill package generated with UseFactoryProfile, when its manifest is validated, then it holds the required fields id, version, name, purpose, inputs and outputs of the SkillManifest of docs/reference/schemas/asset-manifests.schema.json, validates against that schema and is contained in the packed package (skill-manifest-v1, ADR-0021 decision 2: a skill release candidate is evaluated on its declared profile).
AC2 Given a function added to a package generated with the profile without a manifest entry, or a manifest entry without a function, when the unit tests run, then the drift test fails with the function named (skill-manifest-v1, model/services/control-plane/AgentRegistryService.yaml keeps the dependency closure of a release).
AC3 Given the generated manifest, when it is inspected, then compatibility.libraries lists the pinned packages, tests the test projects and evaluations the suites to run, and it holds no evaluation result, because the evidence of ADR-0021 decision 3 is an artifact the gate attaches to the release.
AC4 Given a package generated without UseFactoryProfile, when its output is compared with the output of the current template, then the two are equal: it holds no manifest file, its central package management pins no Factory package and the skill id and purpose parameters change no file; UseFactoryProfile and the two parameters appear in model/template-parameters/connectsoft-aiskills-library.yaml after the next inventory (docs/architecture/adr/0028-one-repository-and-deployable-per-service.md amendment on the Factory profile switch: off by default, so other generations do not change).
Traces: adrs ADR-0002, ADR-0021
Traces: descriptors skill-manifest-v1
Depends on feature:contracts-package
Sources model/components.yaml, model/templates.yaml, model/template-parameters/connectsoft-aiskills-library.yaml, model/services/control-plane/AgentRegistryService.yaml, docs/reference/schemas/asset-manifests.schema.json, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-650 Skill manifest in the generated package contract Under UseFactoryProfile the generated package carries a SkillManifest with id, version, name, purpose, inputs, outputs, requires, compatibility.libraries, tests and evaluations as docs/reference/schemas/asset-manifests.schema.json defines them, produced from the template parameters and kept beside the code, with the functions of the package as its inputs and outputs; the manifest is what AgentRegistryService takes as a Skill release candidate with the package hash in its closure, and the evaluation record of ADR-0021 is attached by the gate, not by the package. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1346 UseFactoryProfile, the skill id and purpose parameters and the packed manifest file implementation The template configuration defines the boolean parameter UseFactoryProfile, off by default, and parameters for the skill id and the purpose that take effect only under it. Under the profile the project file of the generated library packs the manifest file into the package and the central package management pins the contracts package from which the schema is read; without the profile neither the manifest file, the pack entry nor the pin is generated. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1347 Schema validation, manifest drift and unchanged-default tests fixture The unit test project of a package generated with the profile holds a test that validates the manifest against the SkillManifest schema and a test that compares the functions of the package with the manifest entries and fails with the differing function named. The template repository holds a comparison that generates a package without the profile and fails when its files differ from the recorded output of the current template or when its central package file names a Factory package. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1348 Verify the manifest against the schema and the drift test verification Generate a package with UseFactoryProfile, validate its manifest against docs/reference/schemas/asset-manifests.schema.json, add a function without a manifest entry and run the tests, then generate a package without the profile and run the comparison; the validation passes, the drift test fails by name and the default output equals the current template, which proves AC1 to AC4 of AIFACTORY-US-309 (skill-manifest-v1). ConnectSoft.AISkillsLibraryTemplate

AIFACTORY-US-310: AI skills library template: under UseFactoryProfile every AIFunction declares a tool descriptor, runs under the scope of the caller and is exposed through the MCP library

enabling · persona asset-maintainer As an asset maintainer, I want the functions of a generated skill package to be governed tools that run under the scope of their caller, so that no function of a skill is reachable outside the governed tool path.

The template exposes its functions in two ways: as AIFunctions an agent calls in process, and through its own wrapper LibraryTemplateAgentMcpTool, registered together with a Microsoft Learn MCP client by one extension. Neither path knows a tenant, a project or a side-effect class. ADR-0022 makes every tool an MCP capability with a descriptor in the tool registry and sends every call through the governed executor, and the MCP library of this epic authenticates every server by default and passes the scope of the authenticated caller to the tool handler. This PBI puts the governed tool path under the parameter UseFactoryProfile that AIFACTORY-US-309 defines. Under the profile every AIFunction has a tool-descriptor-v1 document with its JSON schema, its side-effect class, its timeout, retry and rate limits and its audit requirements, packed beside the manifest. The manifest itself holds no descriptor: its requires is an object of three string arrays and the schema admits no further property, so requires.tools names by tool id only the tools the skill calls, which in a generated package are the supporting functions its orchestrator calls, and the functions the package exposes are named in inputs and outputs as AIFACTORY-US-309 defines. A function executes under the tenant and project the scope accessor of ConnectSoft.Extensions.AI.Factory.Abstractions delivers; the package pins that library and defines no scope type. A function resolved or called without a scope is refused. The wrapper of the template is replaced by exposure through ConnectSoft.Extensions.ModelContextProtocol with authorization on, so a call without a token is refused by the library and the template carries no server code of its own. The Microsoft Learn client stays in the template as a sample of an MCP client; under the profile it is not registered as a tool of the skill. Without the profile the package keeps the wrapper and the registration of today.

Acceptance criteria

AC1 Given a package generated with UseFactoryProfile, when it is packed and inspected, then every AIFunction has a tool-descriptor-v1 document packed beside the manifest with schema, side-effect class, timeout, retry, rate limit and audit fields, a test fails when a function has none, requires.tools of the manifest holds tool ids only, every one of which resolves to a packed descriptor, and the manifest still validates against docs/reference/schemas/asset-manifests.schema.json (tool-descriptor-v1, ADR-0022 decision 3).
AC2 Given the same package and no scope in the scope accessor, when a function is resolved from the container or invoked, then the call is refused with an error that names the missing scope; with a scope the function runs and its invocation record carries the tenant and the project (tool-invocation-v1, ADR-0022 decision 2).
AC3 Given a host that maps the functions of the package through the MCP library, when a client calls a tool without a token, then the call is refused with 401, and the generated code holds no LibraryTemplateAgentMcpTool and no server code of its own (ADR-0022 decision 4: authentication is on by default; docs/architecture/adr/0022-mcp-as-tool-protocol.md).
AC4 Given a package generated without UseFactoryProfile, when its output is compared with the output of the current template, then it is unchanged: it keeps the wrapper and the registration of today and holds no descriptor document (ADR-0022; tool-descriptor-v1 is required only under the profile; model/template-parameters/connectsoft-aiskills-library.yaml).
Traces: adrs ADR-0022
Traces: descriptors tool-descriptor-v1, tool-invocation-v1
Depends on AIFACTORY-US-309, feature:component-mcp, feature:component-extensions-ai, feature:contracts-package
Sources model/components.yaml, model/template-parameters/connectsoft-aiskills-library.yaml, docs/reference/schemas/asset-manifests.schema.json, docs/architecture/adr/0022-mcp-as-tool-protocol.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1349 A tool descriptor document per function, packed beside the manifest contract Under UseFactoryProfile, the parameter AIFACTORY-TASK-1346 defines, every AIFunction of the generated package has a tool-descriptor-v1 document with schema, side-effect class, limits and audit fields in the shape of the contracts package, and the project file packs the documents beside the manifest; requires.tools of the manifest names by tool id the tools the skill calls and holds no descriptor. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-651 AIFunctions as governed tools under the scope of the caller implementation Under the profile every AIFunction executes under the tenant and project scope the pinned scope accessor delivers and refuses a call without scope; the wrapper LibraryTemplateAgentMcpTool of the template is replaced by exposure through ConnectSoft.Extensions.ModelContextProtocol with authorization on; the Microsoft Learn client stays as a sample client and is not registered as a tool of the skill. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1350 Dependency injection and MCP refusal tests of the generated package fixture The test projects of a package generated with the profile hold a dependency injection test that proves a function cannot be resolved without the scope accessor, an invocation test without scope, a descriptor completeness test, a test that every id in requires.tools resolves to a packed descriptor document, and an acceptance test in which an MCP call without a token is refused with 401. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1351 Verify descriptors, scope refusal and MCP authorization on a generated package verification Generate one package with UseFactoryProfile and one without, build and test both; the tests of AIFACTORY-TASK-1350 pass on the first and the second is unchanged, which proves AC1 to AC4 of AIFACTORY-US-310 (ADR-0022, tool-descriptor-v1). ConnectSoft.AISkillsLibraryTemplate

AIFACTORY-US-311: AI skills library template: redaction uses the Factory data classes, telemetry carries no payload and the embeddings pipeline takes its store from the host profile

enabling · persona asset-maintainer As an asset maintainer, I want a generated skill package to redact, measure and embed on the conventions of the Factory, so that a skill never logs a prompt, never names its own redactor and never chooses a vector store for a tenant.

The template registers its own redactor through Microsoft.Extensions.Compliance and ConnectSoft.Extensions.Compliance, emits activities and meters through LibraryTemplateTelemetry, AgentFrameworkMetrics and LibraryTemplateMetrics, and registers an embeddings pipeline on Microsoft.Extensions.VectorData with a store of its own choice. ADR-0019 decision 3 forbids a prompt, a response or a tool output in a log, a trace or a metric; the Compliance library of this epic carries the Factory data classes and redaction profiles; the observability libraries carry the telemetry conventions as one registration; and ADR-0013 makes the vector backend a profile whose authorized scope is supplied by the trusted host and enforced before selection. This PBI moves the generated package onto those three under UseFactoryProfile. Redaction applies the data classes and the redaction profile of the Compliance library to the request and result records, and the redactor registration of the template is removed under the profile. The activities and meters keep their purpose but take their names, their scope tags and their bounded dimensions from the single registration of the observability libraries, and no prompt, completion, tool output or embedded text is written to a tag, a dimension or a log message. The embeddings pipeline resolves its vector store from the host, which registers the store of its profile; the package registers none, and an upsert or a search without a scope is refused. A telemetry test collects the tags of every activity and compares them with an allow list.

Acceptance criteria

AC1 Given a package generated with UseFactoryProfile, when a request with a field of a Factory data class is processed, then the logged and traced forms of the request and the result are redacted by the profile of the Compliance library and the generated code holds no redactor registration of its own (ADR-0019 decision 3, model/components.yaml row of the Compliance library).
AC2 Given the same package, when a function runs under an activity listener and a meter listener, then the activity and meter names and the scope tags are those of the single registration of the observability libraries, the metric dimensions are bounded, and the telemetry test finds no prompt, completion, tool output or embedded text in any tag, dimension or log message (ADR-0019 decision 3).
AC3 Given a host that registers the vector store of its profile, when the embeddings pipeline of the package upserts and searches, then it uses that store and registers none of its own, and an upsert or a search without a scope is refused, as ADR-0013 decision 1 requires the authorized scope to come from the trusted host.
Traces: adrs ADR-0013, ADR-0019
Depends on AIFACTORY-US-310, feature:component-compliance-factory-classifications, feature:component-observability-factory-conventions
Sources model/components.yaml, model/template-parameters/connectsoft-aiskills-library.yaml, docs/architecture/adr/0013-vector-store-profiles.md, docs/architecture/adr/0019-data-governance.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-652 Redaction, telemetry and embeddings on the Factory conventions implementation Under the profile redaction uses the Factory data classes and redaction profiles of the Compliance library in place of the redactor registration of the template; the activities and meters of LibraryTemplateTelemetry, AgentFrameworkMetrics and LibraryTemplateMetrics follow the single registration of the observability libraries and carry no prompt, completion or tool output (ADR-0019); the embeddings pipeline takes its store from the vector store profile of the host (ADR-0013) and refuses a call without scope. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1352 Payload-absence and redaction tests of the generated package fixture The unit test project of a package generated with the profile holds a telemetry test that compares the tags and dimensions of every activity and meter with an allow list and fails with the tag named, a redaction test over the request and result records, and an embeddings test with an in-memory store registered by the test host. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1353 Verify redaction, payload absence and the host vector store verification Generate a package with UseFactoryProfile, build and run the tests of AIFACTORY-TASK-1352, then add a payload tag to a sample and rerun; the first run passes and the second fails with the tag named, which proves AC1 to AC3 of AIFACTORY-US-311 (ADR-0013, ADR-0019). ConnectSoft.AISkillsLibraryTemplate

AIFACTORY-US-312: AI skills library template: one target-frameworks parameter, the template manifest and symbol catalog of the library template, and pages that describe the code

enabling · persona asset-maintainer As an asset maintainer, I want the parameters and the pages of the AI skills library template to say what the template does, so that a maintainer who reads the pages generates the package the pages describe.

The pages of the template are out of step with its code. The Features page is a copy of the page of the library template: it lists UseDI, UseLogging, UseOptions, UseMetrics and UseTracing, while the template configuration defines useDI, useOptions, useLogging, useMetrics, targetFrameworks, Framework, buildDefinitionNumber and SkipRestore and has no tracing switch; it promises health check endpoints a class library does not host and multi-targeting of two frameworks. The versioning page (TEMPLATE_VERSIONING.md of the template) names Semantic Kernel and two older frameworks, while the README and the code are on the Microsoft Agent Framework, which ADR-0002 chose, and target the framework of the Factory backend. A Framework choice, a targetFrameworks string and a generated override symbol coexist. This PBI reconciles them. The template adopts the target-frameworks parameter of the library template with the same name and semantics, so both library templates are driven the same way, and the Framework choice keeps its meaning as the primary moniker. A generated repository carries the manifest .connectsoft/template-manifest.json with the template id connectsoft-aiskills-library, the package version and the parameter values, and the package carries .template.config/template-manifest.schema.json and .template.config/symbol-catalog.json, in the names and shapes the library template sets. The Features page lists the real parameters and drops what the template does not have; the versioning page names the Agent Framework and the frameworks the template targets.

Acceptance criteria

AC1 Given the template, when a package is generated with the target-frameworks parameter set to the single framework of the Factory backend, then the library and its test projects target that framework only, and the parameter has the name and the semantics the library template defines in model/template-parameters/connectsoft-library.yaml (ADR-0002, model/template-parameters/connectsoft-aiskills-library.yaml lists it after the next inventory).
AC2 Given a generated package, when its repository and the template package are inspected, then .connectsoft/template-manifest.json holds the template id connectsoft-aiskills-library, the package version and every parameter value, and the package holds .template.config/template-manifest.schema.json and .template.config/symbol-catalog.json in the shapes of the library template (ADR-0002, model/backlog/pbis/component-extensions/component-library-template-factory-profile.yaml sets the names).
AC3 Given the pages of the template, when they are compared with the template configuration, then the Features page lists exactly the parameters of model/template-parameters/connectsoft-aiskills-library.yaml, names no tracing switch and no health endpoint, and the versioning page names the Microsoft Agent Framework that ADR-0002 chose and the frameworks the template targets.
Traces: adrs ADR-0002
Depends on feature:component-library-template-factory-profile
Sources model/components.yaml, model/templates.yaml, model/template-parameters/connectsoft-aiskills-library.yaml, model/template-parameters/connectsoft-library.yaml, model/backlog/pbis/component-extensions/component-library-template-factory-profile.yaml, docs/architecture/adr/0002-microsoft-agent-framework-over-semantic-kernel.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1354 Target-frameworks parameter as the library template defines it contract The template configuration replaces the free targetFrameworks string and the generated override symbol by the target-frameworks parameter of the library template, with the same name, values and default; the project files of the library and of the two test projects follow the chosen set and Framework stays the primary moniker. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1355 Template manifest written at generation and symbol catalog exported at pack time implementation The template writes .connectsoft/template-manifest.json into the generated repository with the template id, the package version and every parameter value and preserves it on regeneration; a pack step writes .template.config/symbol-catalog.json beside .template.config/template-manifest.schema.json into the package, in the shapes of the library template. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1356 Features and versioning pages rewritten from the template configuration documentation The Features page lists the real parameters of the template with their defaults and drops UseTracing, the health endpoints and the two-framework claim; the versioning page names the Microsoft Agent Framework and the targeted frameworks and no longer Semantic Kernel. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1357 Verify the single-framework generation, the manifest and the pages verification Generate a package for the single framework, read its manifest back, compare the catalog of the template package with model/template-parameters/connectsoft-aiskills-library.yaml and the Features page with the catalog; the comparisons pass and prove AC1 to AC3 of AIFACTORY-US-312 (ADR-0002). ConnectSoft.AISkillsLibraryTemplate

AIFACTORY-US-313: AI skills library template: the packed template is installed, instantiated across its parameters and for the Factory profile, built and tested before the package publishes

evidence · persona asset-maintainer As an asset maintainer, I want every change of the AI skills library template to be gated by the packages it generates from the packed candidate, so that a template package that would scaffold a skill that does not build or pass never reaches the feed.

This PBI is the gate of the feature. The installer pipeline of the template (azure-pipelines-template.yml of the template) packs the nuspec and pushes the installer package without instantiating the packed candidate, and the repository holds a unit test project and an acceptance test project but no scaffold tests. The gate adds them and runs them through the shared template installer steps of ConnectSoft.AzurePipelines: the installer pipeline calls the shared installer job in place of its own pack and push steps, whose push allows package conflicts today, and switches on the gate hook and the version guard that AIFACTORY-TASK-1426 of the feature component-base-template-findings delivers. The candidate is packed once and installed, and the hook runs the scaffold tests against it after the pack and before the push; they instantiate it across the parameter matrix: useDI, useOptions, useLogging and useMetrics on and off and the values of the target-frameworks parameter, reduced to the pairs of values so that the run stays bounded while every pair of options is covered. The gate and the publication rest on two texts of ADR-0028 and on the epic: the amendment on scaffolding from the published templates (D94) names this feature among the template extensions that precede development, the amendment on the Factory profile switch (D114) admits one additional gating case per declared profile beside the default case, and model/backlog/epics.yaml makes a package that passes its generated-solution gate the completion of the epic. ADR-0021 and ADR-0022 apply only to what the gate checks inside the profile output: the SkillManifest a release candidate is evaluated with and the tool descriptor documents. For each output the pipeline restores, builds in Release, runs the unit and acceptance tests, reads the template manifest back and scans for placeholders that were not replaced; for the profile case it also validates the SkillManifest and the descriptor documents and runs the scope, MCP and payload-absence tests. An output that fails any stage fails the run with the parameter values and the stage named, and the push is not reached. Publication pushes the template package to the ConnectSoft feed with a version that is not yet on the feed, and the version guard, which the template switches on, refuses a repeated version.

Acceptance criteria

AC1 Given a change of the template, when its pipeline runs, then the candidate is packed once and installed, the gate hook of the shared installer steps (AIFACTORY-TASK-1426) runs the scaffold tests, which instantiate it across the matrix of useDI, useOptions, useLogging, useMetrics and the target-framework values and for the Factory profile case, each output is restored, built in Release, tested, checked against its template manifest and scanned for placeholders, and the profile output also passes the validation of its SkillManifest and of its descriptor documents (docs/architecture/adr/0028-one-repository-and-deployable-per-service.md amendments D94 and D114: this feature precedes development and the template pipeline admits one additional gating case per declared profile; ADR-0022 decision 3 for the descriptors; model/template-parameters/connectsoft-aiskills-library.yaml lists the parameters of the matrix).
AC2 Given an output fails any stage, when the pipeline evaluates the run, then the gate hook fails the run with the parameter values and the stage named, no later stage of that output is reported as passed and the push is not reached; a fixture with a planted defect in one output proves the refusal (docs/architecture/adr/0028-one-repository-and-deployable-per-service.md amendment D114; model/backlog/epics.yaml states the gate as the completion of the epic).
AC3 Given every output is green, when the push step runs, then the template package is pushed to the ConnectSoft feed with a version that is not on the feed and the version guard of the shared installer steps, which the template switches on, refuses a repeated version with the reason (model/backlog/epics.yaml: each template publishes a package that passes its generated-solution gate; docs/architecture/catalogs/templates.md keeps the row of the template).
Traces: adrs ADR-0021, ADR-0022
Depends on AIFACTORY-US-309, AIFACTORY-US-310, AIFACTORY-US-311, AIFACTORY-US-312, feature:component-base-template-findings
Sources model/components.yaml, model/backlog/epics.yaml, model/template-parameters/connectsoft-aiskills-library.yaml, docs/architecture/catalogs/templates.md, docs/architecture/adr/0021-quality-gates.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1358 Scaffold test project and the parameter matrix in the installer pipeline operations The template repository gains a scaffold test project that instantiates the installed candidate across the pairwise matrix of the four feature switches and the target-framework values and for the Factory profile case; the installer pipeline file calls the shared installer job of ConnectSoft.AzurePipelines in place of its own pack and push steps, so the candidate is packed once and installed, switches on the gate hook and the version guard of AIFACTORY-TASK-1426 and passes the hook these cases, each named in its output; the push follows only when every case passed, and the guard refuses a version that is already on the feed. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-1359 Planted failing output fixture for the gate fixture A pipeline fixture generates the Factory profile output with a planted manifest defect and asserts that the run fails at the manifest validation stage with the parameter values named and that the push is not reached. ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-653 Pages, parameters and a generated-solution gate reconciled verification One green run and one planted run of the gate: the scaffold tests instantiate the packed template across the parameter matrix and for the Factory profile case, build and test each output and validate the manifests and descriptor documents of the profile output, the planted output stops the run before publication and the green run publishes the package with a verified version, which proves AC1 to AC3 of AIFACTORY-US-313 (ADR-0022, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md). ConnectSoft.AISkillsLibraryTemplate

AIFACTORY-US-121: AI skills library template: skill packages the registry publishes and the agent host loads is delivered and proven on a generated solution

enabling · persona asset-maintainer As an asset maintainer, I want AI skills library template to carry skill packages the registry publishes and the agent host loads, so that it serves compiled skill packages (AIFunctions on the Agent Framework) the registry publishes as Skill assets and the agent host loads without later rework.

This is the integration PBI of the feature. An asset maintainer packs the AI skills library template with the SkillManifest, the Factory profile, the Factory redaction and telemetry, the reconciled parameters and pages and the template manifest, installs the package and instantiates it across its parameters in the installer pipeline. Every generated package builds and passes its tests before the template package is allowed to publish; an output that fails any stage fails the run and blocks publication. The implementation lives in the earlier PBIs of this file; this PBI proves them together on the skill package the Factory builds first. From the published template package a skill package is generated with UseFactoryProfile for the single framework of the Factory backend. It builds unchanged; its SkillManifest validates against the schema and names every function; a function called without scope is refused; an MCP call without a token is refused; and its telemetry carries no payload. The feature is done when that package builds from a fresh install of the published template package. Generating skill packages from skill definitions belongs to the Factory assets epic. Repository of the feature: ConnectSoft.AISkillsLibraryTemplate.

Acceptance criteria

AC1 Given the template repository ConnectSoft.AISkillsLibraryTemplate with the work of this feature, when the template is packed, installed and instantiated in its pipeline, then the generated solution of every case builds and its tests pass before the package publishes with a verified version (ADR-0021, model/components.yaml).
AC2 Given the work of AIFACTORY-TASK-650 (skill manifest in the generated package) is done, then under UseFactoryProfile the generated package carries a SkillManifest as docs/reference/schemas/asset-manifests.schema.json defines it, a test validates it against the schema, a package generated without the profile equals the output of the current template, and the manifest is what AgentRegistryService takes as a Skill release candidate, with the evaluation record of ADR-0021 attached by the gate and not by the package.
AC3 Given the work of AIFACTORY-TASK-651 (AIFunctions as governed tools under the scope of the caller) is done, then under UseFactoryProfile every AIFunction has a tool descriptor document packed beside the manifest, executes under the tenant and project scope of the caller, refuses a call without scope and is exposed through the MCP library with authorization on in place of the wrapper of the template (ADR-0022 decisions 2 to 4).
AC4 Given the work of AIFACTORY-TASK-652 (redaction, telemetry and embeddings on the Factory conventions) is done, then redaction uses the Factory data classes, the activities and meters carry no prompt, completion or tool output (ADR-0019 decision 3), and the embeddings pipeline takes its store from the vector store profile of the host (ADR-0013 decision 1).
AC5 Given the work of AIFACTORY-TASK-653 (pages, parameters and a generated-solution gate reconciled) is done, then the Features page lists the real parameters of model/template-parameters/connectsoft-aiskills-library.yaml, the versioning page names the Agent Framework of ADR-0002, the target-frameworks parameter is the one of the library template, and the scaffold tests instantiate the packed template across the parameter matrix before the package publishes to the ConnectSoft feed.
Traces: adrs ADR-0002, ADR-0013, ADR-0019, ADR-0021, ADR-0022
Depends on AIFACTORY-US-309, AIFACTORY-US-310, AIFACTORY-US-311, AIFACTORY-US-312, AIFACTORY-US-313
Sources model/components.yaml, model/templates.yaml, model/template-parameters/connectsoft-aiskills-library.yaml, model/services/control-plane/AgentRegistryService.yaml, docs/reference/schemas/asset-manifests.schema.json

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1360 Generate a Factory skill package from the published template and run its tests verification A probe installs the published template package, generates a skill package with UseFactoryProfile for the single framework, builds it in Release unchanged and runs its manifest, scope, MCP and payload-absence tests; the run proves AC2 to AC4 of AIFACTORY-US-121 on the published package (ADR-0019, ADR-0022). ConnectSoft.AISkillsLibraryTemplate
AIFACTORY-TASK-667 Verify aiskills-library-template-skill-packages-delivered by running the declared command verification Run dotnet build -c Release and dotnet test -c Release --no-build on the authoring solution and on every output of the parameter matrix after the published package is installed; they pass and prove AC1 to AC5 of AIFACTORY-US-121. ConnectSoft.AISkillsLibraryTemplate