| 1. |
|
| 2. |
|
| 3. |
|
| 4. |
|
| 5. |
|
| 6. |
Governs when the AI should ask clarifying questions before generating output, what to ask, and how to ask efficiently. Defines trigger conditions (ambiguous feature, undefined scope, missing data source, access control unspecified, technical conflict, existing code not provided), what questions to ask per topic, and how to frame questions with built-in assumptions.
|
| 7. |
|
| 8. |
|
| 9. |
|
| 10. |
|
| 11. |
|
| 12. |
|
| 13. |
|
| 14. |
|
| 15. |
|
| 16. |
|
| 17. |
|
| 18. |
|
| 19. |
|
| 20. |
|
| 21. |
|
| 22. |
|
| 23. |
|
| 24. |
|
| 25. |
|
| 26. |
|
| 27. |
|
| 28. |
|
| 29. |
|
| 30. |
|
| 31. |
|
| 32. |
|
| 33. |
|
| 34. |
|
| 35. |
|
| 36. |
|
| 37. |
|
| 38. |
|
| 39. |
|
| 40. |
|
| 41. |
|
| 42. |
|
| 43. |
|
| 44. |
|
| 45. |
|
| 46. |
|
| 47. |
|
| 48. |
|
| 49. |
|
| 50. |
|
| 51. |
|
| 52. |
|
| 53. |
|
| 54. |
|
| 55. |
|
| 56. |
|
| 57. |
|
| 58. |
|
| 59. |
|
| 60. |
|
| 61. |
|
| 62. |
|
| 63. |
|
| 64. |
|
| 65. |
|
| 66. |
|
| 67. |
|
| 68. |
|
| 69. |
|
| 70. |
|
| 71. |
|
| 72. |
|
| 73. |
|
| 74. |
|
| 75. |
|
| 76. |
|
| 77. |
|
| 78. |
|
| 79. |
|
| 80. |
|
| 81. |
|
| 82. |
|
| 83. |
|
| 84. |
|
| 85. |
|
| 86. |
|
| 87. |
|
| 88. |
|
| 89. |
|
| 90. |
|
| 91. |
|
| 92. |
|
| 93. |
|
| 94. |
|
| 95. |
|
| 96. |
|
| 97. |
|
| 98. |
|
| 99. |
|
| 100. |
|
| 101. |
|
| 102. |
|
| 103. |
|
| 104. |
|
| 105. |
|
| 106. |
|
| 107. |
|
| 108. |
|
| 109. |
|
| 110. |
|
| 111. |
Sequenced build patterns for the six most common Centralpoint workflows spanning multiple features: (1) Content Module with Display, (2) Form Submission with Workflow, (3) Data Import with Enrichment, (4) AI Bot Deployment, (5) API Integration with Display, (6) User Access Control. Prescribes correct build order, skill per step, and integration handoff points.
|
| 112. |
This skill provides help documentation for Centralpoint modules features.
|
| 113. |
|
| 114. |
|
| 115. |
|
| 116. |
|
| 117. |
|
| 118. |
|
| 119. |
|
| 120. |
|
| 121. |
|
| 122. |
|
| 123. |
|
| 124. |
|
| 125. |
|
| 126. |
|
| 127. |
|
| 128. |
|
| 129. |
|
| 130. |
|
| 131. |
|
| 132. |
|
| 133. |
|
| 134. |
|
| 135. |
|
| 136. |
|
| 137. |
|
| 138. |
|
| 139. |
|
| 140. |
|
| 141. |
|
| 142. |
|
| 143. |
|
| 144. |
|
| 145. |
|
| 146. |
|
| 147. |
|
| 148. |
|
| 149. |
|
| 150. |
|
| 151. |
This skill provides help documentation for Centralpoint data management features.
|
| 152. |
|
| 153. |
|
| 154. |
|
| 155. |
|
| 156. |
|
| 157. |
|
| 158. |
|
| 159. |
|
| 160. |
|
| 161. |
|
| 162. |
|
| 163. |
|
| 164. |
|
| 165. |
|
| 166. |
|
| 167. |
|
| 168. |
|
| 169. |
|
| 170. |
|
| 171. |
|
| 172. |
|
| 173. |
|
| 174. |
|
| 175. |
|
| 176. |
|
| 177. |
|
| 178. |
|
| 179. |
|
| 180. |
|
| 181. |
|
| 182. |
|
| 183. |
|
| 184. |
|
| 185. |
|
| 186. |
|
| 187. |
|
| 188. |
|
| 189. |
|
| 190. |
|
| 191. |
|
| 192. |
|
| 193. |
|
| 194. |
|
| 195. |
|
| 196. |
|
| 197. |
|
| 198. |
|
| 199. |
|
| 200. |
|
| 201. |
|
| 202. |
|
| 203. |
|
| 204. |
|
| 205. |
|
| 206. |
|
| 207. |
|
| 208. |
|
| 209. |
|
| 210. |
|
| 211. |
|
| 212. |
|
| 213. |
|
| 214. |
|
| 215. |
|
| 216. |
|
| 217. |
|
| 218. |
This skill documents the **complete 6-file pattern** for building a Centralpoint ACTION EXT Module Designer: a data-centric grid with checkbox selection wired to a 3-step Wizard Action Form that performs bulk operations (Change Attributes, Move Modul
|
| 219. |
Centralpoint modules can be customized through a **Module Configuration XML** file (CustomModuleConfig.xml) that defines additional fields beyond the base module schema. Custom fields that extend beyond the standard release are stored in the `cpsys_D
|
| 220. |
This skill defines the mandatory format for all The model skill files. Follow these rules
|
| 221. |
This skill provides help documentation for Centralpoint taxonomy features.
|
| 222. |
Magic Quadrant for Digital Experience Platforms Published: 17 January 2018 Analyst(s): Jim Murphy, Gene Phifer, Gavin Tay, Mike Lowndes Organizations are looking to use DXPs as they move from web-centric to more pervasive, multichannel digital experiences. This Magic Quadrant will help those responsible for a range of customer-, employee- and partner- facing initiatives find the most suitable vendor for their needs. Market Definition/Description
|
| 223. |
|
| 224. |
Complete mental model of the Centralpoint platform: nine functional layers (Data, Import, Enrichment, Automation, Presentation, Interaction, Integration, AI, Governance), full feature dependency map showing what each feature depends on and what it feeds into, and a key decision guide for choosing between similar approaches (Standard vs EXT, Web API vs CP API Services, Data Governance vs Data Triggers, etc.).
|
| 225. |
Defines mandatory fields for every AI interaction audit log -- execution ID, prompt version, model used, skills loaded, user identity, risk level, disclaimer status, human review outcome, and output hash. Governs retention periods by risk level and regula
|
| 226. |
AI Prompt Manager -- How to Configure a Prompt
Unknown
Centralpoint — AI Integration Layer, AI Prompt Manager — Module Architecture
Everyone: All Users
4/9/2026
Relevance: 7
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Rank Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
cpsys_Attributes:AlternativeUrl Column
/CpScript
12/31/9999 11:59:59 PM
AI Prompt Manager, prompt rule, system prompt, prompt template, required skills, write-back, delivery method, query type
4/9/2026 2:37:23 PM
|
| 227. |
Defines when and how AI-generated output must include disclaimer text. Applies to high-stakes output categories including legal documents, clinical summaries, financial narratives, compliance assessments, and public communications.
|
| 228. |
Defines when AI must stop autonomous processing and escalate to a human reviewer. Prevents AI from making consequential decisions without human oversight. Applies to compliance assessments, personnel actions, legal determinations, and high-confidence-thre
|
| 229. |
Defines plain language communication standards for content directed at the general public, employees without specialized domain knowledge, or any audience with mixed education levels. Compliance with the Plain Writing Act for government contexts. 6th-8th
|
| 230. |
Defines email formatting, structure, and tone standards for all AI-generated email content including broadcast emails, triggered notifications, workflow emails, and one-to-one communications. Covers subject line writing, body structure, call-to-action for
|
| 231. |
Template and framework for creating an organizational AI Use Policy -- the foundational governance document defining permitted uses, prohibited uses, user rights, liability limitations, and the complaint process. This is the policy document the AI Output
|
| 232. |
Defines the communication style for content directed at C-suite executives and board members. Brevity, precision, and decision-orientation are the governing principles. Bottom-line-up-front structure. No preamble. Action-oriented conclusion.
|
| 233. |
Defines communication style for content directed at developers, solutions architects, data engineers, IT administrators, and other technical audiences. Precision, completeness, and actionability. Technical terminology expected and appropriate. Code sample
|
| 234. |
**STOP.** Before generating ANY of the following, read and apply the restrictions below:
|
| 235. |
|
| 236. |
Ensure every Excel spreadsheet generated for Centralpoint module import uses
|
| 237. |
|
| 238. |
Centralpoint AI Data Flow Animation Centralpoint AI Data Flow Animated Lottie-style plumbing view: data starts from enterprise sources on the left, flows through Centralpoint SQL, Skills, Prompts, Compound Engineering, and GRAIL, then outputs through chatbots to users. Activity flows back into AI 360 to build inertia. Scheduled daily aggregation 1. Data Sources 365 Microsoft 365 Word, Excel, PowerPoint, Outlook SP SharePoint / O365 Lists, pages,
|
| 239. |
**COPYRIGHT (C) 2025 Oxcyon, Inc. -- Centralpoint Digital Experience Platform**
|