How to Enable the Agent Assets Folder in SharePoint

Ready 01

What Skills Do in a SharePoint Agent

A skill is a reusable set of instructions that helps an agent perform a particular type of work. Instead of explaining the same process every time you use the agent, you can create a skill that describes the expected behaviour, the information it should use, and the result it should produce.

For example, a skill could explain how an agent should:

• Review a document and identify the main action items
• Answer common questions about an internal process
• Prepare a standard meeting summary
• Organise information into a consistent format
• Guide a user through a repeated business task
• Use specific SharePoint content when responding to a request

The purpose is not to make the agent more complicated. The purpose is to give it useful context in a form that can be reused. A well prepared skill can make responses more consistent, especially when several people are using the same agent.

It helps to think of the Skills folder as a controlled library of working instructions. The files stored there should support a clear purpose. If you add unrelated material, old instructions, or duplicate versions, it may become more difficult to understand which guidance the agent should rely on.

Skills are instructions, not ordinary documents

A normal document may contain information for people to read. A skill should be prepared with the agent in mind. It needs to explain what the agent should do and how it should respond when the skill is relevant.

That difference is important. A long policy document may contain useful information, but it may not tell the agent how to apply that information. A stronger skill gives the agent a clear role, a defined task, and practical boundaries.

Before creating a skill, ask a few simple questions:

• What task is this skill supposed to support?
• Who will use the agent?
• What information should the agent consider?
• What should the response look like?
• What should the agent do when the information is incomplete?
• How will I test whether the skill is working properly?

These questions help you avoid adding instructions simply because they seem useful. A skill should solve a real problem and be easy to maintain when the process changes.

Ready 02

Readiness Check Before You Begin

Before opening Site Contents, it is worth completing a quick readiness check. This can save time if the folder is not visible or if you reach a permissions barrier later in the process.

You do not need to prepare a large library before trying this feature. It is usually better to begin with one small, focused skill. You can then test the result, improve the wording, and add more skills after the basic process is working.

Confirm the site you are working in

SharePoint can contain many sites, libraries, lists, and workspaces. Make sure you are in the site where the agent assets should be stored. If you activate the feature in the wrong site, the folder may appear somewhere other than where you expect it.

Look at the site name, the site navigation, and the content you are working with. If your organisation uses similar names for different sites, confirm the address or ask the site owner before changing any settings.

Check your access

The steps in this guide include opening Site Settings and Site Collection Features. These areas may be restricted. If you cannot see the settings, or if the activation control is unavailable, you may need help from a SharePoint administrator or site owner.

Do not treat a missing folder as proof that SharePoint is not working. It may simply mean that the feature has not been activated, or that your account does not have the required access to view or manage it.

Ready 03

Find the Agent Assets Folder in Site Contents

The first place to check is the Site Contents page. This page provides an overview of the main applications, libraries, and content areas connected to the SharePoint site.

Open the SharePoint site you want to use. From the site navigation or settings menu, open Site Contents. Once the page loads, look through the available folders and libraries for an item named Agent Assets.

The basic path is:

1. Open the correct SharePoint site
2. Open Site Contents
3. Look for the Agent Assets folder
4. Open Agent Assets
5. Look for the Skills folder

If the Agent Assets folder is visible, you can open it and continue to the Skills folder. The folder structure is designed to separate the assets used by the agent. For this process, the area you need is the Skills folder.

If you do not see Agent Assets, do not create a replacement folder with a similar name straight away. A manually created folder may not work in the same way as the feature provided by SharePoint. First, check whether the Agent Assets feature is active.

What the folder structure tells you

Once the feature is available, you should see an Agent Assets folder within Site Contents. Inside that folder, there is a Skills folder where you can place the skills you want the agent to use.

This structure creates a simple separation between general site content and content intended to support agents. It also gives you a more obvious place to review the instructions that have been added.

Keeping skills in the correct folder matters for two reasons. First, it makes the content easier to manage. Second, it helps ensure that the agent can find the assets that are intended for it. Adding a file to an unrelated document library may make it difficult for the agent or other administrators to identify its purpose.

Ready 04

Enable Agent Assets When the Folder Is Missing

If Agent Assets is not visible in Site Contents, the next step is to open Site Settings and check the site collection features. This is where you can see whether the Agent Assets feature has been activated.

From the SharePoint site, open Site Settings. Depending on the SharePoint experience and your permissions, you may reach this through the settings menu. Within Site Settings, look for Site Collection Features and open it.

The Site Collection Features page contains a list of available features and their current status. Scroll through the list or use the page search if it is available. Look for the feature named Agent Assets.

When the feature is not active, the page should provide an Activate control beside it. Select Activate and wait for SharePoint to complete the change.

After activation, the status should change to Active. This status confirms that the feature has been enabled for the site collection.

Activation checklist

• Open the correct SharePoint site
• Open Site Settings
• Select Site Collection Features
• Locate Agent Assets
• Check whether the feature is inactive
• Select Activate
• Wait until the status displays Active
• Return to Site Contents
• Confirm that Agent Assets is now visible

It is useful to pause after activation and confirm the result rather than immediately moving on. Open Site Contents again and look for the new folder. In some situations, you may need to refresh the page before the change appears.

If activation is not available

If you can see Agent Assets but cannot select Activate, the most likely issue is permission. SharePoint does not allow every user to change site collection features. Contact the person who manages the site and explain which feature needs to be enabled.

When requesting help, provide the site name and the name of the feature. A clear request is easier to action than a general message saying that the agent folder is missing.

You can use a message such as:

Could you please check whether the Agent Assets feature is active for our SharePoint site? The Agent Assets folder is not visible in Site Contents, and I do not have access to activate site collection features.

If the feature appears to be active but the folder still does not appear, refresh Site Contents and confirm that you are using the same site where the feature was enabled. It is easy to activate a feature in one site and then continue looking at another site in the same SharePoint environment.

Ready 05

Open the Skills Folder

Once Agent Assets is active and visible, return to Site Contents. Open the Agent Assets folder, then open the Skills folder inside it.

This is the location where you can place the skills needed by your agent. Before adding anything, take a moment to inspect the folder and confirm that you are in the right location.

A simple navigation check looks like this:

1. Site Contents
2. Agent Assets
3. Skills

When you reach the Skills folder, you are ready to add the instructions that support your agent. The exact method for creating or uploading a skill may depend on the SharePoint and agent tools available in your environment, but the important foundation is the folder location.

Do not fill the folder with every document related to your business. Start with the instructions that are directly connected to the agent task. A smaller collection of relevant material is easier to review and test than a large collection with no clear structure.

Prepare the first skill carefully

Your first skill should have one clear purpose. For example, a skill that helps prepare weekly updates should not also contain unrelated instructions for customer complaints, recruitment, and document archiving.

Keep the content direct. Explain the role the agent should perform, the steps it should follow, and the format it should use for its response.

A practical skill can include the following sections:

• Purpose: Explain what the skill helps the agent do
• Audience: Identify who will use the result
• Inputs: Describe the information the agent should consider
• Process: List the steps the agent should follow
• Output: Describe the expected response format
• Limits: Explain what the agent should not assume
• Escalation: State when the agent should ask for human help

For example, if the skill is designed to create a meeting summary, the instructions could tell the agent to identify decisions, list assigned actions, record due dates when they are available, and clearly mark anything that needs confirmation.

That is more useful than simply uploading a document called Meeting Notes and expecting the agent to understand how it should process every possible meeting.

Ready 06

Build a Simple Launch Checklist for Your Skill

Adding a skill to the folder is only one step. A reliable setup also needs a basic launch check. This helps you identify missing instructions before other people depend on the agent.

Before adding the skill

• Confirm the skill has one main purpose
• Remove outdated instructions
• Use approved business information
• Check that names, roles, and processes are current
• Decide what the agent should do when information is missing
• Prepare realistic questions for testing

While adding the skill

• Open the Agent Assets folder from Site Contents
• Open the Skills folder
• Add the prepared skill in the supported format
• Use a clear file name that explains the purpose
• Check that the file has finished uploading or saving
• Confirm that the skill is visible in the folder

After adding the skill

• Test a normal request related to the skill
• Test a request with incomplete information
• Test a request that is outside the skill scope
• Check whether the agent follows the expected format
• Review the response for accuracy and unnecessary assumptions
• Ask a second person to try the same task

Testing with only one perfect example can give you a false sense of confidence. A skill may work well when every detail is present but produce an unclear answer when the user leaves out an important piece of information.

Include ordinary questions, unusual questions, and questions that the agent should not answer directly. This will help you understand whether the instructions are clear enough and whether the boundaries are practical.

Useful test: Ask the agent to complete the task with one important detail missing. A good skill should guide the agent to ask for clarification instead of inventing an answer.

Keep ownership clear

Every useful skill should have an owner. That person does not need to manage every interaction with the agent, but they should be responsible for checking the instructions when the underlying business process changes.

Without an owner, skills can become outdated. A process may change, a team may adopt a new approval step, or a document may move to another location. The agent will continue using the instructions it has unless someone reviews and updates them.

Record a small amount of management information with each skill:

• Name of the responsible person or team
• Date the instructions were last checked
• Business process supported by the skill
• Source documents used to prepare the instructions
• Next review date

This does not need to become a large administration project. A simple ownership record can prevent confusion later, particularly when several people contribute skills to the same agent.

Ready 07

Prepare the Skill for a Controlled Launch

Once the skill is saved in the Skills folder, the next step is to treat it like a small business process rather than just another document. A good launch checks what the agent should do, what information it can use, how it should respond, and what must happen when the request falls outside its instructions.

Confirm the skill is ready

Before asking anyone to use the skill, complete a final readiness check. This is particularly important when the skill relates to customer information, finance, human resources, legal matters, or any process that requires an approved response.

• Confirm the skill has a clear and useful name.
• Check that the filename is easy to understand and find later.
• Make sure the instructions describe one main task.
• Confirm the intended audience is stated clearly.
• Check that all required source documents are available.
• Remove old examples, draft notes, and unrelated instructions.
• Confirm that the skill does not request information the user cannot provide.
• Check that the output format matches the way people will use the result.
• Include guidance for missing, unclear, or conflicting information.
• Record the owner and the next review date.

A useful test is to give the skill to someone who was not involved in writing it. Ask that person to explain what the skill does, which information it needs, and what result it should produce. If the explanation is unclear, the skill probably needs another edit before launch.

Key insight: A skill should make a process easier to follow, not hide a complicated process behind an impressive answer.

Check the dependency chain

Skills do not work in isolation. The quality of the result depends on the relationship between the instructions, the connected SharePoint content, the user request, and the permissions available to the agent.

For example, a skill for preparing a supplier summary may depend on a supplier register, a current purchasing policy, and a standard reporting template. If one of those sources is missing or out of date, the skill may still respond, but the response may not be reliable.

Before launch, write down the key dependencies in plain language. This makes it easier for another person to maintain the skill in the future.

This dependency check is also useful when a skill appears to be working correctly. A successful test today does not prove that the skill will continue working after a document is moved, renamed, replaced, or restricted.

Ready 08

Test the Skill with Realistic Requests

A skill should be tested with the type of requests people will actually make. Testing only one perfect example can create false confidence. Real users may leave out important details, use different words, combine several requests, or ask questions that the skill was never designed to answer.

Start with a normal request

Begin with a complete request that includes all the information the skill expects. This establishes a simple baseline and helps you confirm that the basic instructions are being followed.

Imagine the skill is designed to help a team prepare a project update. A normal request might provide the project name, current status, completed work, open issues, upcoming activities, and the intended audience. The response should then follow the agreed structure without adding unsupported information.

Review the result against the skill instructions rather than judging it only by appearance. Ask the following questions:

• Did the agent understand the purpose of the request?
• Did it use the approved information?
• Did it follow the required order and format?
• Did it distinguish facts from suggestions?
• Did it avoid making assumptions?
• Did it identify information that still needs confirmation?
• Was the language suitable for the intended audience?

Test incomplete information

The next test should deliberately leave out one important detail. This shows whether the skill asks a sensible question or quietly fills the gap with an invented answer.

For example, if a request asks for a project update but does not include the current delivery date, the agent should identify the missing date. It should not create a date based on previous projects or present an estimate as a confirmed commitment.

A well written skill can tell the agent what to do when information is incomplete. You might include wording such as:

• Ask the user for the missing information before preparing the final response.
• Mark an item as awaiting confirmation when it cannot be verified.
• Use only the information supplied by the user or available in approved sources.
• Do not guess dates, prices, names, approvals, or policy requirements.
• Explain which missing detail is preventing a complete answer.

This type of behaviour is often more valuable than a polished answer. It helps users understand what needs attention and reduces the risk of an incorrect response being copied into a business document.

Test a request outside the skill

Every skill needs a boundary test. Ask a question that sounds related but is outside the defined purpose. The agent should either explain that the skill does not cover the request or direct the user to a more appropriate process.

For instance, a skill that prepares a purchasing summary should not approve an expenditure, interpret a legal agreement, or make a final supplier selection unless those tasks are explicitly authorised and supported by the instructions.

Useful boundary tests include:

• A request for a decision rather than a summary.
• A request involving confidential information.
• A request that conflicts with an approved policy.
• A request that needs professional or management approval.
• A request involving a source document that the agent cannot access.
• A request that combines the skill with an unrelated task.

The result should be calm and useful. The agent does not need to provide a long refusal. It should explain the limitation, identify what it can do, and show the next appropriate step.

Compare results across different wording

Users will not all ask for the same thing in the same way. Test the skill with several versions of the request. Change the order of the information, use common alternative terms, and try both a short and detailed request.

This helps reveal whether the skill understands the business task or only responds well to one carefully prepared sentence. If small changes produce very different results, improve the skill by adding clearer context, examples, or output rules.

Keep a simple test record. It does not need to be complicated. A spreadsheet or page in the SharePoint site can record the test date, request used, expected behaviour, observed result, and action required.

Ready 09

Review Accuracy, Safety, and User Experience

Testing should cover more than whether the agent produces an answer. The response must also be accurate enough for its intended use, safe for the information involved, and simple for people to understand.

Accuracy review

Compare important statements in the response with the approved source material. Pay particular attention to figures, dates, names, status labels, policy references, and instructions that could lead someone to take action.

If the skill summarises content, check that it does not remove a qualification that changes the meaning. A short summary can be misleading if it leaves out an exception, condition, approval requirement, or deadline.

It is helpful to classify the output into three groups:

• Confirmed information: Information directly supported by the request or an approved source.
• Suggested action: A useful recommendation that is clearly presented as a suggestion.
• Information requiring review: A point that cannot be confirmed or needs a person to decide.

Ask the skill to use these distinctions when the process requires careful review. This gives users a clearer understanding of what they can rely on and what they need to check.

Safety and privacy review

Consider what could happen if the skill receives sensitive information or produces an incorrect result. The skill should not encourage users to paste unnecessary personal, financial, medical, security, or confidential information into a request.

Include practical limits in the instructions. For example, the skill may tell users to provide a reference number instead of a full customer record, or to remove information that is not needed for the task.

Also check whether the output itself could expose information to people who do not need to see it. A summary intended for a project team may not be suitable for a wider audience. The skill should identify the intended audience and remind the user to review sharing permissions where appropriate.

For higher risk processes, include a human approval step. The agent can prepare a draft, organise information, or identify missing details, while a responsible person makes the final decision.

User experience review

A technically correct response can still be difficult to use. Read the output as though you are seeing it for the first time. Is the main answer easy to find? Are the next actions clear? Does the response contain unnecessary detail? Does it use terms that the intended audience understands?

Ask a small group of users to complete a practical task with the skill. Watch for hesitation, repeated questions, or workarounds. These observations can reveal problems that are not obvious when the skill is tested by its author.

Useful user feedback questions include:

• Was it clear what information you needed to provide?
• Did the response use a format that suited your work?
• Did you know which details needed checking?
• Did the skill save time compared with the usual process?
• What part of the response was confusing?
• What did you expect the skill to do that it did not do?

Ready 10

Use a Simple Launch Checklist

A launch checklist keeps the final review practical. It also creates a shared understanding between the person who wrote the skill, the site owner, and the people who will use it.

Before launch

• Confirm the correct SharePoint site.
• Confirm access to Agent Assets and the Skills folder.
• Check that the skill has one clear purpose.
• Confirm the approved source material.
• Remove duplicate or outdated instructions.
• Check the filename and document title.
• Include the intended audience.
• Include required inputs and expected outputs.
• Define what the agent must not do.
• Add instructions for incomplete information.
• Add an escalation path.
• Record the owner and review date.

During launch

• Upload the final version to the Skills folder.
• Confirm that the file appears in the correct location.
• Check that the filename has not been changed unexpectedly.
• Allow time for the agent to recognise the updated content.
• Run a complete example.
• Run an incomplete example.
• Run a boundary example.
• Record unexpected behaviour.
• Tell users what the skill is designed to support.

After launch

• Collect feedback from early users.
• Review the first outputs for accuracy.
• Check whether users are supplying the required information.
• Look for repeated misunderstandings.
• Update the skill when the process changes.
• Record changes in a simple version history.
• Confirm that the source documents remain available.
• Schedule the next formal review.

Do not treat launch as the moment the file is uploaded. The real launch happens when people can use the skill consistently and understand when its output needs human review.

Ready 11

Maintain Skills as Business Processes Change

A skill is only useful while its instructions reflect the current process. Policies change, teams change, systems change, and documents are replaced. Without ownership, a skill can quietly become misleading.

Assign one accountable owner

There may be several people who contribute to a skill, but one person should be accountable for keeping it accurate. The owner does not need to perform every update. Their responsibility is to monitor the process, coordinate changes, and confirm that the skill remains suitable.

Record the following information within the skill or in a related register:

• Skill name and purpose.
• Business area responsible for the process.
• Named owner.
• Contributors and reviewers.
• Approved source documents.
• Intended users.
• Known limitations.
• Date of the last review.
• Date of the next review.
• Summary of recent changes.

This information reduces the time needed to investigate a problem. If a user reports that an answer looks wrong, the owner can quickly check which source material was used and when the skill was last reviewed.

Use meaningful updates

When a process changes, update the skill with the change rather than adding a note that conflicts with an older instruction. Conflicting instructions make it harder for the agent and the user to identify the correct process.

Read the full skill after making an update. A new rule may affect another section, an example, or the escalation guidance. It is better to remove an obsolete instruction completely than to leave it in place and hope that the newer wording takes priority.

Keep a short change record. It might include the date, the person who made the change, the reason for the change, and the test that was completed. This is especially useful for skills that support regulated or highly structured work.

Set a review rhythm

The review interval should match the risk and rate of change. A frequently changing operational process may need a monthly review. A stable internal process may only need a review every few months. A review should also happen whenever a related policy, form, system, approval rule, or source document changes.

At each review, confirm:

• The skill still supports an active business process.
• The source documents are current.
• The intended users have not changed.
• The output format is still useful.
• The escalation path still reaches the right person.
• The limitations are still accurate.
• The test examples still represent real requests.

If a skill is no longer needed, do not leave it in the Skills folder without explanation. Follow the organisation’s document management process to archive or remove it, and record why it is no longer active.

Ready 12

Troubleshoot Common Problems

Most problems can be traced to access, location, content quality, or expectations. A structured check is usually faster than repeatedly rewriting the skill.

The agent does not appear to use the skill

First, confirm that the file is in the correct Skills folder and that the upload completed successfully. Check the filename, file type, and document content. Then confirm that the agent has access to the SharePoint site and that the relevant feature is active.

Next, test a request that clearly matches the skill purpose. A skill may not be used when the request is too general or when several skills appear to cover the same task. Make the purpose more specific and include terms that users are likely to use.

The response is too general

A general response often means the skill does not provide enough process detail. Add the required inputs, the expected sequence, the audience, and a sample output. Explain what a useful response must contain rather than only describing the task in broad terms.

For example, instead of saying “prepare a project update”, specify that the response must include current status, completed work, open risks, decisions required, upcoming activities, and items awaiting confirmation.

The agent invents missing information

Strengthen the limits section. Tell the agent to identify missing details, ask a question, and mark unverified information clearly. Add a test case with missing information so the expected behaviour is easy to check.

It can also help to include a short instruction that says the agent must not create names, dates, figures, approvals, or policy interpretations that are not supported by the available information.

Users are unsure how to start

Add a short request example near the beginning of the skill. Show the information a user should provide and the type of result they can expect. Keep the example realistic and avoid using confidential business details.

You can also provide a simple prompt pattern such as:

• State the task.
• Provide the relevant project, customer, or process name.
• Include the current information.
• Explain who will read the result.
• Identify any deadline or required format.

The skill gives inconsistent formatting

Define the headings, order, length, tone, and level of detail required in the response. If the format matters, include a short example. Avoid giving several competing examples unless each one has a clear purpose.

Remember that consistency does not mean every response must sound identical. The structure can remain stable while the wording changes naturally according to the request.

Ready 13

Create a Reusable Skill Structure

A consistent structure makes skills easier to write, review, and compare. The following format works well for many business tasks.

Purpose

Explain what the skill helps the agent do and why the process matters. Keep this section short. The purpose should describe the business task, not the technology behind it.

Audience

Identify who will use the result and who will read it. A response for a team member may be different from a response for a customer, manager, supplier, or executive audience.

Inputs

List the information the user should provide and the information the agent may find in approved SharePoint content. Explain which inputs are essential and which are optional.

Process

Describe the steps the agent should follow. Use direct instructions and place them in a sensible order. If one step depends on another, state that dependency clearly.

Output

Define the response structure. Include headings, tables, lists, wording, length, and any required labels. Explain how the agent should present unknown or unconfirmed information.

Limits

State what the skill must not do. This may include making approvals, offering professional advice, exposing sensitive information, changing records, or answering unrelated questions.

Escalation

Explain when a person should become involved and identify the appropriate owner, team, or process. A useful escalation instruction tells the agent what to say and what information to pass on.

Examples

Include one normal example, one incomplete example, and one boundary example when appropriate. These examples should demonstrate the expected behaviour rather than simply repeat the instructions.

Ready 14

Build a Small Library of Skills

Once the first skill is stable, you can create additional skills for related tasks. Resist the temptation to put every instruction into one large document. Smaller skills are easier to test and maintain.

Good candidates include tasks that are repeated, structured, and supported by reliable source material. Examples include preparing meeting summaries, organising project updates, explaining an internal procedure, checking whether a request includes required information, or creating a first draft from an approved template.

Avoid creating a skill for every minor variation of the same task. If two processes share most of their instructions, consider whether one skill with a clear choice of output would be easier to manage. On the other hand, separate skills may be better when the audiences, risks, approvals, or source documents are different.

Use clear names that describe the task. A name such as “Project Update Summary” is more useful than “Assistant Instructions Version Two”. Consistent naming also makes the Skills folder easier to manage as it grows.

Ready 15

Practical Questions About SharePoint Skills

Can a skill replace a business policy?

No. A skill can help the agent apply or explain an approved process, but it should not replace the official policy. The policy remains the authoritative source. If there is a conflict, the skill should direct the user to the approved policy or responsible owner.

Should a skill contain every detail about a process?

Not necessarily. The skill should contain enough instruction to guide the agent reliably. Detailed reference information can remain in approved SharePoint documents. The skill should explain which sources to use and how to apply them.

How many skills should be added at once?

Start with one focused skill and test it properly. Adding several untested skills at the same time makes it difficult to identify which instruction or source caused a problem. A small, reliable library is more useful than a large collection that users do not trust.

What should happen when source documents disagree?

The skill should tell the agent not to choose silently. It should identify the conflict, refer to the document dates or authority where available, and ask the user to confirm the correct source. The responsible process owner should then resolve the conflict.

Can users edit a skill whenever they want?

Access should follow the organisation’s normal SharePoint governance. Limit editing to people who understand the process and are responsible for its accuracy. Users should be able to provide feedback without automatically changing the instructions.

What is the most important test?

Test a realistic request that is missing an important detail. This shows whether the skill can handle normal uncertainty. A trustworthy skill should make missing information visible instead of hiding the gap with a confident sounding answer.

Ready 16

Keep the Operating Routine Simple

The most sustainable approach is to include skills in the normal process of managing SharePoint content. When a policy or procedure changes, the owner checks whether the related skill also needs an update. When users report an unclear result, the issue is recorded and reviewed rather than fixed informally in a separate message.

A simple operating routine can look like this:

• Review the skill when its source material changes.
• Collect user feedback in one agreed location.
• Test important updates before publishing them.
• Keep the owner and review date visible.
• Remove instructions that no longer apply.
• Keep examples free from confidential information.
• Record significant changes for future reference.

This routine keeps the Skills folder useful without creating unnecessary administration. The aim is not to document every possible situation. The aim is to give the agent dependable guidance for a defined task, while making it clear when a person needs to review the result.

When a skill is focused, tested, owned, and connected to current SharePoint content, it becomes a practical asset for everyday work. It can help people begin with the right information, follow a consistent process, and produce a clearer first result without pretending that human judgement is no longer required.

Ready 17

Frequently Asked Questions

What is the Skills folder used for in a SharePoint agent?

The Skills folder stores reusable instructions that help a SharePoint agent complete specific tasks consistently. Skills can guide the agent when reviewing documents, answering common questions, preparing meeting summaries or organising information.

Why can’t I see the Agent Assets folder in Site Contents?

The Agent Assets folder may not appear automatically on every SharePoint site. If it is missing, the Agent Assets feature may need to be activated from Site Settings. You may also lack the permissions required to view or manage site features.

What permissions are needed to use Agent Assets?

You generally need enough access to open Site Settings, manage site features and work with site content. If the activation option is unavailable, contact your SharePoint administrator or site owner.

How is a skill different from a normal document?

A normal document is usually written for people to read, while a skill is written to guide an agent. It should clearly explain the agent’s role, the task to perform, the information to use, the expected response format and what to do when information is incomplete.

How should I start creating skills for my agent?

Begin with one small, focused skill that supports a real business task. Use approved source material, define how the agent should respond and prepare example questions or tasks to test whether the skill works as intended. Once it has been tested, you can refine it and add more skills.